Mailing List Archive

Expirations: PGPfreeware 6.0 vs. GPG 0.4.2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

A friend of mine created a keypair in PGPfreeware 6.0 (Windows), and set
an expiration time of 1 year. However, when GPG sees the public key, it
thinks it expired many, many moons ago. GPG output:

$ gpg --edit-key otherguy
gpg (GnuPG) 0.4.2; Copyright (C) 1998 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.


gpg: key E2445CD9.64: expired at Tue Jan 05 00:00:00 1971 GMT
pub 1024D/E2445CD9 created: 1998-10-27 expires: 1971-01-05 trust: -/e
sub 2048g/92FFB6F4 created: 1998-10-27 expires: never
(1) Other Guy <otherguy@some.host.com>

Any ideas about this? Is PGP in the wrong here, or is GPG (one of them is
definitely wrong ;-)? I have no idea about the Windows product he's using,
so maybe this is a simple misconfiguration on his part?

- --
Edward S. Marshall <emarshal@logic.net> /> Who would have though that we -o)
http://www.logic.net/~emarshal/ // would be freed from the Gates of /\\
Linux Weenie, Open-Source Advocate </ hell by a penguin named "Tux"? _\_v

Linux labyrinth 2.1.125 #9 SMP Sat Oct 17 14:46:24 CDT 1998 i586 unknown
8:35pm up 11 days, 6:38, 4 users, load average: 0.13, 0.11, 0.04

-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.2 (GNU/Linux)
Comment: For info finger gcrypt@ftp.guug.de

iEYEARECAAYFAjY31ioACgkQod/ZJKejQQr4NACePTvuvwU+fKc6FrqgarhKZFW2
6cIAn1jKrB2s0fKEYkA9v4FsqFYAu+a4
=XE33
-----END PGP SIGNATURE-----
Re: Expirations: PGPfreeware 6.0 vs. GPG 0.4.2 [ In reply to ]
On Wed, Oct 28, 1998 at 08:42:48PM -0600, Edward S. Marshall wrote:
> A friend of mine created a keypair in PGPfreeware 6.0 (Windows), and set
> an expiration time of 1 year. However, when GPG sees the public key, it
> thinks it expired many, many moons ago. GPG output:
>
> $ gpg --edit-key otherguy
> gpg (GnuPG) 0.4.2; Copyright (C) 1998 Free Software Foundation, Inc.
> This program comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions. See the file COPYING for details.
>
>
> gpg: key E2445CD9.64: expired at Tue Jan 05 00:00:00 1971 GMT
> pub 1024D/E2445CD9 created: 1998-10-27 expires: 1971-01-05 trust: -/e
> sub 2048g/92FFB6F4 created: 1998-10-27 expires: never
> (1) Other Guy <otherguy@some.host.com>
>
> Any ideas about this? Is PGP in the wrong here, or is GPG (one of them is
> definitely wrong ;-)? I have no idea about the Windows product he's using,
> so maybe this is a simple misconfiguration on his part?

It seams gpg always says expires: never with sub keys. I created
a D/g key with expire time of 4 years. gpg --edit-key says

pub 1024D/46DE66CA created: 1998-10-29 expires: 2002-10-28 trust: -/u
sub 1024g/9A25B7DB created: 1998-10-29 expires: never

I changed the expire time of the subkey to 1 year but it still says

sub 1024g/9A25B7DB created: 1998-10-29 expires: never

but gpg -vv --list-keys 46DE66CA shows

:public key packet:
version 4, algo 17, created 909626405, expires 0
:signature packet: algo 17, keyid DE8CC16746DE66CA
hashed subpkt 2 len 5 (sig created 1998-10-29)
hashed subpkt 9 len 5 (key expires 2002-10-28)
:public sub key packet:
version 4, algo 16, created 909626435, expires 0
:signature packet: algo 17, keyid DE8CC16746DE66CA
hashed subpkt 2 len 5 (sig created 1998-10-29)
hashed subpkt 9 len 5 (key expires 1999-10-29)

I have included it below.

Another strange thing is: a key which I signed but associate only
marginal trust with shows: trust: m/f
Another which I didn't sign but fully trust shows: trust: f/q

Other wishes for the todo list:
- prefs editor (but I think that is already on the list)
- possibility to create keys with other than the buildin
cyphers


-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GNUPG v0.4.2 (FreeBSD)
Comment: For info finger gcrypt@ftp.guug.de

mQGiBDY3zCURBACy6YKMkbUm/TI00DriU9H1Spzi4uOVBCH50+PQshxbEDQUZdk5
ruSOWAVXvwLePSCtgyJqzDrlAFTJ+1tPsh+zetTQ9AIr7fddtp2JRWDxrcad1MYG
m7iETJS2yPKbGg9nnbBbRocGCYfzXz1tw7JJq/7JpdMz6FUUbVd4K9xhUwCgymvi
SuEKUxBrUo9qfkTBJe0oQFsD/ipr11KNLa9PVhwV5GDmSgReUEyPQiM/l9fUe+51
xxAsSNvGsMJBu9Bp/SzEjKm7NcBcyc7fxAfKHcX38vrAD2IqwhUiUftrNuNLlRZN
b/EQh3gAyVlqHVnjsRqRxAkRefJpTWeGYETttdNRzHmG51UdGxLaAdWjNo4io6c9
Od0IA/9CM+PU8moolPDmahPoXSpdUNITZdJiaMugAxZHvIAcVs2VFvJYeUIkMa72
40o6bMhLnwXwUAZ9yqhbbO4o1lYBx0c+lc2jDg0jURomMljgfhZpRT/G2ra2Yq8F
EfBDyPRV0QHluIcX5Brq5uqCpTLGGuso3jpx79CaDuuVD06XDrQtRnJhbmsgSi4g
QmVja21hbm4gPGZyYW5rQGJhcmRhLmFnYWxhLmhhcnouZGU+iF0EExECAB0FAjY3
zCUFCT28me8DCwQDBRUDAgYBAxYCAQIXgAAKCRDejMFnRt5mygvTAJ9wI7gKflba
a/aXLlPLG0O60g1A2ACfRZVO3t20eMH4Dc93NeK0/36qg22JAJUDBRA2N86y+fU6
s2bcOX0BAQP9A/9hb2zYqRmUh96TeOKStT9Qmx7T7tMLxUMm0UdCLLY3NO9kmK1L
QtjOXvOwaB003ha0q8pwJqgP6d7BZ3x/tssUO6xw8l06uQnH0Mt62mWBQTUxsxks
u/QfMhWVFW/VvmSz2wBy/K6eNQqmfsswe4QffubvMPHl63Z7Z62iXoqAiLQtRnJh
bmsgSi4gQmVja21hbm4gPGZyYW5rQHZvZ29uLmFnYWxhLmhhcnouZGU+iF0EExEC
AB0FAjY3zT0FCT28me8DCwQDBRUDAgYBAxYCAQIXgAAKCRDejMFnRt5myu8AAKCx
C6HEM52tIq0PLu2DEvbOc+LupwCaAjOWvAqXkRDcOiJ/eVsfMoZIUKmJAJUDBRA2
N865+fU6s2bcOX0BAZSvBACltsYhlrprYUzhav6/eTKLaP3+JkASyTy95fHqI3oy
ea+5PtHBQyIm/yxtCWk+BrNo92M/apqRQfI+7pslun+2CgcQb/UfJs+1ozJr4Zwl
kI2hIKN7TaNySV/WNzp7ELquSGFk8TLzoxaCWsUGSacpN0irirQXXt0gm2acsXRL
XbkBDQQ2N8xDEAQAqPBYLPQBKCcgysbYu2lpMwWmVqzwBNNO5g9i/1EEuEGaxVX1
aZODi3onlorEAhmeUuKbI5++T7dCWXaT/eZfGSzaVpaFM4mUdMTtWuBz3VphDtYu
SRp2fymaxi9UMjVc5sZE3tEFFAyEDHeZZ6kDfJkkjRrjtKVDIiqqzS2BjA8AAwUD
+wV9GYbafVtLWwKOeYzBQiWjz1zFLhRS50dk98hZFPoh/WIAzm/mduo7b1zEj2kr
PEyNDniRXunZ4T3eGhIX92ICLnte40I8WNSL2ydczK6spt+CWwUonzUctBTnoXta
1408XC8y9G+QkVyuwiiFTSw33GuUDRgN2wKkyuJZfq3xiEwEGBECAAwFAjY3zV0F
CTgZANkACgkQ3ozBZ0beZsquEACfeRT9njYwkEzDUCABESHA3BB7SQwAnRJ2+TKC
6tMTCbHL1bP/08IkD4nG
=ojFF
-----END PGP PUBLIC KEY BLOCK-----

Frank
Re: Expirations: PGPfreeware 6.0 vs. GPG 0.4.2 [ In reply to ]
"Edward S. Marshall" <emarshal@logic.net> writes:

> A friend of mine created a keypair in PGPfreeware 6.0 (Windows), and set
> an expiration time of 1 year. However, when GPG sees the public key, it
> thinks it expired many, many moons ago. GPG output:

Already fixed in the CVS and release 0.4.2 .

You can change the expiration time with --edit-key and the command
"expire". Select the which you want to change.


Werner