From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Changing GPG encryption for GCC copy
Date: Wed, 07 Nov 2012 10:50:52 +0100 [thread overview]
Message-ID: <87sj8loi6b.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87ip9hyegx.fsf@rss01.mhs.man.ac.uk>
On Wed, 07 Nov 2012 09:00:46 +0000, Matt wrote:
> I can't help feel I'm missing something here - should the fact that
> I've signed and encrypted an email also mean that I should be able to
> decrypt it (i.e, message should be encrypted with both my key and the
> recipients).
I think this is often done by configuring gpg to encrypt for your key as
well, perhaps by setting default-recipient and hidden-encrypt-to in
~/.gnupg/gpg.conf
(It's been a while since I added those options to my configuration, that
is why I am being vague.)
Best regards,
Adam
--
"Man skal være godt skør for at blive programmør Adam Sjøgren
Sidde og trykke på taster til den dag hvor man dør asjo@koldfront.dk
Jeg bliver ved til den dag hvor fornuften går fløjten
Så ryger tasterne på hylden til fordel for sprøjten"
next prev parent reply other threads:[~2012-11-07 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 9:00 Matt Ford
2012-11-07 9:50 ` Adam Sjøgren [this message]
2012-11-07 10:54 ` Matt Ford
2012-11-07 10:44 ` Christopher Schmidt
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=87sj8loi6b.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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).