From: Paul Stodghill <stodghil@CS.Cornell.EDU>
Subject: Re: PGP verifying NoCeM messages
Date: 15 Jan 1997 09:48:51 -0500 [thread overview]
Message-ID: <mlzpybuh7w.fsf@hoho.cs.cornell.edu> (raw)
In-Reply-To: David Moore's message of 14 Jan 1997 21:29:53 -0800
>>>>> "David" == David Moore <dmoore@UCSD.EDU> writes:
David> I ended up turning of the pgp verifying, but couldn't you
David> put their keys in your local ring and solve the key server
David> problems?
Yes, this is exactly what I have done. Works just fine: NoCeM verification
is acceptable fast and doesn't fail.
--
Paul Stodghill <stodghil@cs.cornell.edu>
http://www.cs.cornell.edu/home/stodghil/home.html
next prev parent reply other threads:[~1997-01-15 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-10 17:16 Lance A. Brown
1997-01-14 23:32 ` Lars Magne Ingebrigtsen
1997-01-15 4:25 ` Mark Eichin
1997-01-15 5:29 ` David Moore
1997-01-15 14:35 ` Alan Shutko
1997-01-15 14:48 ` Paul Stodghill [this message]
1997-01-15 14:14 ` Lance A. Brown
1997-01-15 14:58 ` Paul Stodghill
1997-01-15 15:55 ` Lance A. Brown
1997-01-16 23:05 ` Lars Magne Ingebrigtsen
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=mlzpybuh7w.fsf@hoho.cs.cornell.edu \
--to=stodghil@cs.cornell.edu \
/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).