From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Canonical methods for digitally signing and verifying
Date: 15 Dec 2000 19:01:35 +0100 [thread overview]
Message-ID: <vaf66klsgw0.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <ltzohxd1of.fsf@asfast.com>
On 15 Dec 2000, Lloyd Zusman wrote:
> (1) ... digitally sign outgoing email via gpg.
> (2) ... digitally encrypt outgoing email via gpg.
In the message buffer, the MML menu has a Security submenu. Just look
up the right functions.
> (3) ... verify digitally signed incoming email.
> (4) ... decrypt incoming email that was encrypted either via pgp or
> gpg.
Does `W s' do the trick?
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2000-12-15 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 17:39 Lloyd Zusman
2000-12-15 18:01 ` Kai Großjohann [this message]
2000-12-15 18:50 ` Lloyd Zusman
2000-12-15 18:57 ` ShengHuo ZHU
2000-12-15 21:08 ` Lloyd Zusman
2000-12-15 21:30 ` ShengHuo ZHU
2000-12-15 21:45 ` Lloyd Zusman
2000-12-17 14:04 ` Simon Josefsson
2000-12-17 17:40 ` Lloyd Zusman
2000-12-17 20:55 ` Charles Sebold
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=vaf66klsgw0.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).