Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: Michael Sperber <sperber@deinprogramm.de>
Cc: ding@gnus.org
Subject: Re: Encrypt gcc copy with own key
Date: Tue, 26 May 2009 07:10:57 +0900	[thread overview]
Message-ID: <a29d3033-54c5-447f-af6b-aaabe1326854@broken.deisui.org> (raw)
In-Reply-To: <y9l4ov9mipr.fsf@deinprogramm.de> (Michael Sperber's message of "Mon, 25 May 2009 15:10:24 +0200")

>>>>> 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".

Regards,
-- 
Daiki Ueno



  reply	other threads:[~2009-05-25 22:10 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 [this message]
2009-05-28 10:39   ` Michael Sperber
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=a29d3033-54c5-447f-af6b-aaabe1326854@broken.deisui.org \
    --to=ueno@unixuser.org \
    --cc=ding@gnus.org \
    --cc=sperber@deinprogramm.de \
    /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).