From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: How to automatically send public key?
Date: Tue, 16 Oct 2012 22:32:04 +0200 [thread overview]
Message-ID: <87sj9e17ln.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87ehky6yg2.fsf@sklar.v.cablecom.net>
On Tue, 16 Oct 2012 20:53:17 +0200, Marius wrote:
> What is 'good practice' when using public key encryption (via GnuPG
> for PGP/MIME)? Attaching public keys? Putting a message in the
> signature that the public key can be retrieved from a keyserver?
I think putting it on a keyserver is sufficient.
Just my 25 cents,
Adam
--
"A cat has nine lives, but a bullfrog croaks Adam Sjøgren
every day." asjo@koldfront.dk
prev parent reply other threads:[~2012-10-16 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 18:53 Marius Hofert
2012-10-16 20:32 ` Adam Sjøgren [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=87sj9e17ln.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).