Gnus development mailing list
 help / color / mirror / Atom feed
From: "Lance A. Brown" <labrown@splat.niehs.nih.gov>
Cc: ding@ifi.uio.no
Subject: Re: PGP verifying NoCeM messages
Date: Wed, 15 Jan 1997 09:14:23 -0500	[thread overview]
Message-ID: <3058.853337663@splat.niehs.nih.gov> (raw)
In-Reply-To: Your message of "Tue, 14 Jan 1997 18:32:35 EST." <m2enfnzvcc.fsf@proletcult.slip.ifi.uio.no>

Lars Magne Ingebrigtsen  writes:

> After fetching the keys once, the PGP verification itself seems to be
> pretty quick.  The problem I had in this area was that all the PGP
> key servers I tried were so slow in answering that Mailcrypt would
> time out and give up.  And then, on the next NoCeM article, it would
> try to fetch the key anew.  And time out.  And...

I noticed that too initially.  One NoCeM'ers key was not on the key
server I was using so things were taking forever whenever one of his
articles came through.

My concern now is that there are a LOT of NoCeM messages waiting to be
processed in the morning and it often take 5+ minutes for all the PGP
verification to occur.  This is on an R4000 100Mhz SGI Indy.  Is there
a significant risk of NoCeM spoofing?

--[Lance]


  parent reply	other threads:[~1997-01-15 14:14 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
1997-01-15 14:14   ` Lance A. Brown [this message]
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=3058.853337663@splat.niehs.nih.gov \
    --to=labrown@splat.niehs.nih.gov \
    --cc=ding@ifi.uio.no \
    /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).