Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@acm.org>
Subject: Re: security: Encrypted mail in the archive
Date: Tue, 01 May 2001 13:17:12 +0200	[thread overview]
Message-ID: <E14uY9Y-0004Pk-00@dahaIM.dyndns.org> (raw)
In-Reply-To: <kp7l011u8b.fsf@utip202.cs.utwente.nl>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

Today, Jaap-Henk Hoepman <hoepman@cs.utwente.nl> wrote:
> P.S.: Andreas, what method do you use to encrypt your mail? I don't
> seem to recall seeing this behaviour using pgp and mailcrypt.

I'm using gpg with gpg.el, but I have just tracked down the place where
it goes wrong: my customisation. I have it archive mails and news before
processing mime stuff (for attachments), which also catches pgpmime
processing. This is done via:

(defadvice gnus-inews-do-gcc 
  (around gnus-news-do-gcc-inhibit-body-encoding  first activate)
  (let ((message-inhibit-body-encoding t))
    ad-do-it))

Alright, I commented it out. Let's see now what gnus does.

[silence, as I restart Xemacs and send a test mail]

Yes, now it appears in the archive, encrypted as it is supposed to be
(with the receipient's public key).

Alright, the first point (unencrypted messages in the archive) was a
local configuration error, but I'd really like messages I send encrypted
to be encrypted such that I can read it (as in, with my public key) in
the archive. It looks a little tricky, can it be done?

regards,
-- 
Andreas Fuchs, <asf@acm.org>, <d96001@htlwrn.ac.at>, antifuchs

[-- Attachment #2: Type: application/pgp-signature, Size: 231 bytes --]

  reply	other threads:[~2001-05-01 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-29 14:48 Andreas Fuchs
2001-04-29 17:30 ` Florian Weimer
2001-05-01  7:37   ` Jaap-Henk Hoepman
2001-05-01 11:17     ` Andreas Fuchs [this message]
2001-05-01 11:33       ` Simon Josefsson
2001-05-01 16:51         ` Andreas Fuchs
2001-05-01 14:27       ` Charles Sebold
2001-05-01 12:16     ` Florian Weimer
2001-05-01 12:59       ` Karl Kleinpaste
2001-05-01 11:08 ` Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E14uY9Y-0004Pk-00@dahaIM.dyndns.org \
    --to=asf@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).