> > You'll see output like the following:
> >
> > [-- PGP output follows (current time: Mon Nov 22 16:54:17 1999) --]
> > gpg: Signature made Wed Aug 11 11:36:48 1999 MDT using RSA key ID 98645519
> > gpg: requesting key 98645519 from pgp5.ai.mit.edu ...
> > gpg: public key is 43099 seconds newer than the signature
> > gpg: key 98645519: invalid self-signature
> > gpg: public key is 43476 seconds newer than the signature
> > gpg: key 98645519: invalid self-signature
> > gpg: key 98645519: no valid user IDs
> > gpg: this may be caused by a missing self-signature
> > gpg: Total number processed: 1
> > gpg: w/o user IDs: 1
> > gpg: Can't check signature: public key not found
> > [-- End of PGP output --]
> >
> > e.
> >
> > P.S.
> > Jeremy, you should sign your key. ;-)
Heh. It's signed, but for some reason the date on the sig was earlier than
the creation date of the key (apparently a date-change snafu on the box I
created it on).
Anyway, people report this to me about once a month... the solution is to
get my key(s) from http://jblosser.firinn.org/pgp.key instead of the key
servers. I've tried updating the version on the servers with no success so
far.
--
Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/
-----------------+-------------------------+------------------------------
"If Microsoft can change and compete on quality, I've won." -- L. Torvalds
PGP signature
