From: Michael Sperber <sperber@deinprogramm.de>
To: Daiki Ueno <ueno@unixuser.org>
Cc: ding@gnus.org
Subject: Re: Encrypt gcc copy with own key
Date: Thu, 28 May 2009 12:39:13 +0200 [thread overview]
Message-ID: <y9liqjlfr5a.fsf@deinprogramm.de> (raw)
In-Reply-To: <a29d3033-54c5-447f-af6b-aaabe1326854@broken.deisui.org> (Daiki Ueno's message of "Tue, 26 May 2009 07:10:57 +0900")
Daiki Ueno <ueno@unixuser.org> writes:
>>>>>> In <y9l4ov9mipr.fsf@deinprogramm.de>
>>>>>> Michael Sperber <sperber@deinprogramm.de> wrote:
>
>> I often archive a copy of an encrypted e-mail. Once upon a time, I
>> wondered how to do this without encrypting the archive copy with the
>> recipient's key (which I don't have). Reiner Steib gave some advice
>> here:
>
>> http://article.gmane.org/gmane.emacs.gnus.general/66847
>
>> Somehow, I seem to remember that his idea worked. Looking back at my
>> archived copies, however, they are all un-decryptable. Tracing through
>> the code, it's clear the gcc copy is explicitly encrypted using the
>> recipient's key. So I think there's ultimately a bug somewhere.
>
> This is not a bug of Gnus, but of his suggestion. The default recipient
> shall be used only if the recipient is not specified (see the GnuPG
> manual).
>
> Try "encrypt-to <your key ID>" instead of "default-recipient-self".
Doesn't work for me - tracing through the code, I see that the recipient
key (i.e. not mine) is *explicitly* used for archiving the Gcc copy.
The key is propagated from one invocation of `mml2015-epg-encrypt' to
the next via the `mml2015-epg-recipients' message option.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
next prev parent reply other threads:[~2009-05-28 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 13:10 Michael Sperber
2009-05-25 22:10 ` Daiki Ueno
2009-05-28 10:39 ` Michael Sperber [this message]
2009-05-28 11:02 ` Daiki Ueno
2009-06-04 8:19 ` Michael Sperber
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=y9liqjlfr5a.fsf@deinprogramm.de \
--to=sperber@deinprogramm.de \
--cc=ding@gnus.org \
--cc=ueno@unixuser.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).