CAcert Code Development list.

[Faramir <faramir.cl AT gmail.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

El 23-06-2011 11:30, 
ulrich AT cacert.org
 escribió:
> Dear Developers,
> 
> https://bugs.cacert.org/view.php?id=911
> frequently reports receives support that the adding GPG keys
> function is broken by adding wrong expire date to
> the signed keys.

  I'm not sure, but the signatures on my keys are OK, even if the site
says the signatures on my keys (not the keys) already expired on 1971. I
just renewed one signature, to check it, and this is what I found:

:signature packet: algo 17, keyid D2BB0D0165D0FD58
        version 4, created 1308873995, md5len 0, sigclass 0x10
        digest algo 2, begin of digest 86 1a
        hashed subpkt 2 len 4 (sig created 2011-06-24)
        critical hashed subpkt 3 len 4 (sig expires after 1y1d0h0m)
        hashed subpkt 26 len 29 (policy: http://www.cacert.org/cps.php)
        subpkt 16 len 8 (issuer key ID D2BB0D0165D0FD58)
        data: [160 bits]
        data: [158 bits]

  So, it was signed today, and will expire in 1 year 1 day.

  IMHO, as far as the signature is right, there is no need to stop that
service, after all, people will check the signatures on the user's key,
not what the user's account at CAcert says.

  Best Regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJOA9djAAoJEMV4f6PvczxACKYH/RgjuVRZRUH70AApjKa9d5Sw
fnDL56/MQuPOYr8FroaGZpRylrD046QcEYv1jCo7tVmdE8N5ORs7VsrLR5+WikbP
zZ4a/VekvyliSrD882RrSWHtAVUq1trZKwldYX/d0AC65FF9gsFJ1yA5tRCKHC3i
j5V4Vepf4iJc18TfVjH+H8bZUpID1omyX8HhPbbb+JNm3oWAFKPrY2gozpILYk4K
Gg1NLCczpw7P+rElRyqdXJs5CwTKoQBGvJbFGjH6hGrlWOxNvrm8QNuOzOzposQH
RSlDK1Df+Ajl0fbymSRcLIZ4iW56SmKvKaKOsF/ribOYkfzY+xdiopHGrWubvgI=
=RJ7e
-----END PGP SIGNATURE-----