Exact timestamps may be bad

[disastry@saiknes.lv]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

David Shaw wrote:

[...]
> If zero is used for the timestamp (i.e. 1/1/1970),
> then there is no way to even get a guess about the real setting of the
> clock.
> 
> GnuPG will refuse to validate such a signature ("public key is
> 1027635505 seconds newer than the signature"), unless the
> --ignore-time-conflict option is used to override this check.  PGP
> seems to not mind either way, and will dutifully report that the
> signature was "made" on 1/1/1970.

so set timestamp to the same time (or 1 second above) as public key generation (signing?) time.
then gpg shoul validate it.

__
Disastry  http://disastry.dhs.org/
http://disastry.dhs.org/pgp <----PGP plugins for Netscape and MDaemon
 ^----PGP 2.6.3ia-multi06 (supports IDEA, CAST5, BLOWFISH, TWOFISH,
      AES, 3DES ciphers and MD5, SHA1, RIPEMD160, SHA2 hashes)
-----BEGIN PGP SIGNATURE-----
Version: Netscape PGP half-Plugin 0.15 by Disastry / PGPsdk v1.7.1

iQA/AwUBPUVlnTBaTVEuJQxkEQOwlwCbBJN6MNe4zHve+fPCkFcAGsg2V6IAnjGY
bhAuG5WHvph2kpBGBdzpiozt
=y0K/
-----END PGP SIGNATURE-----