From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Possibly OT: problem with gpg.el
Date: 26 Jan 2001 17:46:58 +1100 [thread overview]
Message-ID: <87hf2mg68t.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <863de6c2es.fsf@duchess.twilley.org> (Jack Twilley's message of "25 Jan 2001 21:23:23 -0800")
Jack Twilley <jmt+usenet@tbe.net> writes:
>
> 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? :-)
Well, I don't have a solution within XEmacs (or Gnus), but...
,----[ ~/.gnupg/options ]
| # Options for GnuPG
|
| [...]
|
| # GnuPG can import a key from a HKP keyerver if one is missing
| # for sercain operations. Is you set this option to a keyserver
| # you will be asked in such a case whether GnuPG should try to
| # import the key from that server (server do syncronize with each
| # others and DNS Round-Robin may give you a random server each time).
| # Use "host -l pgp.net | grep www" to figure out a keyserver.
| keyserver www.keyserver.net
|
| # The environment variable http_proxy is only used when the
| # this option is set.
|
| honor-http-proxy
`----
This works for me. gpg will fetch unknown keys on it's very own.
Er, I do use the mailcrypt code rather than gpg.el to drive gpg but I
doubt that will make a meaningful difference...
Daniel
--
Never stop questioning -- curiosity has its own reason for existence.
-- Albert Einstein
next prev parent reply other threads:[~2001-01-26 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 5:23 Jack Twilley
2001-01-26 6:46 ` Daniel Pittman [this message]
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=87hf2mg68t.fsf@inanna.rimspace.net \
--to=daniel@rimspace.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).