From: Jack Twilley <jmt+usenet@tbe.net>
Subject: Possibly OT: problem with gpg.el
Date: 25 Jan 2001 21:23:23 -0800 [thread overview]
Message-ID: <863de6c2es.fsf@duchess.twilley.org> (raw)
I'm really liking the whole gpg experience, and there's only one thing
that's keeping me from working on auto-validation of all PGP-signed
messages -- the fact that there seems to be no way to auto-fetch
unknown keys.
Am I being clueless here? Should I try to write some elisp? What do
I do? :-)
Jack.
--
Jack Twilley
jmt at tbe dot net
http colon slash slash www dot tbe dot net slash tilde jmt slash
next reply other threads:[~2001-01-26 5:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 5:23 Jack Twilley [this message]
2001-01-26 6:46 ` Daniel Pittman
2001-01-27 3:56 ` Jack Twilley
2001-01-26 19:28 ` Colin Marquardt
2001-01-27 3:59 ` Jack Twilley
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=863de6c2es.fsf@duchess.twilley.org \
--to=jmt+usenet@tbe.net \
/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).