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, 04 Jun 2009 10:19:54 +0200 [thread overview]
Message-ID: <y9lk53s1kd1.fsf@deinprogramm.de> (raw)
In-Reply-To: <a69a5317-5f68-40a2-8d9a-2022e2816b35@broken.deisui.org> (Daiki Ueno's message of "Thu, 28 May 2009 20:02:31 +0900")
Daiki Ueno <ueno@unixuser.org> writes:
>>>>>> In <y9liqjlfr5a.fsf@deinprogramm.de>
>>>>>> Michael Sperber <sperber@deinprogramm.de> wrote:
>
>> > Try "encrypt-to <your key ID>" instead of "default-recipient-self".
>
>> Doesn't work for me
>
> It works for me. [...] "encrypt-to sperber@deinprogramm.de" in
> gpg.conf makes your address an *additional* recipient for all the
> outgoing messages, while "default-recipent-self" doesn't.
Ah, thanks for the explanation. The culprit turned out to be a typo in
my gpg.conf, and things are fine now. Many thanks for the help!
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
prev parent reply other threads:[~2009-06-04 8:19 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
2009-05-28 11:02 ` Daiki Ueno
2009-06-04 8:19 ` Michael Sperber [this message]
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=y9lk53s1kd1.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).