gpg expiration date format (was: Re: gpgme op_gen bug)

[Jacob Perkins]

--=-jKfSV+kHiRTF17ehugYf
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Ok, I was actually sending a time_t value.  I think this makes more
sense from a programming and even usability perspective (i.e. using
gnome-date-edit), so maybe gpgme could do interpretation if gnupg
requires a human readable date.

On Sun, 2002-11-10 at 21:56, Marcus Brinkmann wrote:
> On Mon, Nov 11, 2002 at 01:36:36AM +0100, Miguel Coca wrote:
> > On Sun, Nov 10, 2002 at 15:12:22 -0600, Jacob Perkins wrote:
> > > gpgme-0.3.12 seems to have a key generation bug in that even if given=
 an
> > > expiration date, it still generates a key that does not expire.
> >=20
> > Hi Jacob,
> >=20
> > This seems to work for me now, but it looks like it's tricky to get the
> > date string right in the parameters pased to gpgme. The line must be li=
ke
> > this:
> >=20
> > Expire-Date: 2005-01-01
> >=20
> > If you write the date any differently (2005-1-1, 20050101), it won't wo=
rk,
> > and in some cases even fail silently and create keys that don't expire.
>=20
> All things like this are genuine gnupg issues. gpgme doesn't interpret th=
e
> generation request, it just passes it forward.




--=-jKfSV+kHiRTF17ehugYf
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA9zzCAmq/Go6uOlQ4RAsz1AKCot4/6sgfTN7dWqxpV/ipIviu+jACgkBh4
2I399sSrqo2Nzr1z/6DNjEo=
=xXwU
-----END PGP SIGNATURE-----

--=-jKfSV+kHiRTF17ehugYf--