--expiration bug?

[L. Sassaman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While we're talking about this...

I know I have mentioned this before, but is there any possibility we can
get signature expiration added to GnuPG in the next 1.0.x release?

I don't like to make key certifications without a four year (or
less) expiration, and currently GnuPG doesn't support the signature
expiration time subpacket (subpacket 3, RFC2440:5.2.3.9).

> > program to report error messages "warning: bad parameters" every
> 
> Which version of PGP?  Looks like a PGP problem.

One of the most annoying things about the PGP software is the lack of
meaningful error messages. "Bad parameters" doesn't tell anyone what the
problem is... so who knows where the real problem lies?


> I am working together with the PGP developers to agree on a common
> behaviour for things like this.  They are not defined in the standard.

Common behavior is definately a good thing. Good luck, Werner.
 

- --Len.

__

L. Sassaman

Security Architect             |  "Lose your dreams and you
Technology Consultant          |   will lose your mind."
                               |   
http://sion.quickie.net        |       --The Rolling Stones

-----BEGIN PGP SIGNATURE-----
Comment: OpenPGP Encrypted Email Preferred.

iD8DBQE55Nn5PYrxsgmsCmoRAtzwAKCO3+asYtL3OqHmr0IyJomECBEjrwCgquf+
iYHYWDJWirKaBGaWTzi3XCE=
=d1wh
-----END PGP SIGNATURE-----