[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gpa-dev
Subject:    [issue112] gpgme_key_t: expired not set on an expired key retrieved
From:       Marc Mutz <aegypten-issues () intevation ! de>
Date:       2004-03-11 19:14:57
Message-ID: 1079032496.89.0.406129186055.issue112 () intevation ! de
[Download RAW message or body]

New submission from Marc Mutz <marc@klaralvdalens-datakonsult.se>:

I might not fully understand why the expired flag can't be set right away, =
but =

at least for this key (attached) a validating key listing should show that =
at =

least _something_ is wrong with it. But it's shown as a valid key in the ke=
y =

selection dialog, even after clicking it (ie. doing an expensive validity =

check).

----------
assignedto: werner
files: expired-cert.pem
messages: 501
nosy: jan, marc, werner
priority: bug
status: unread
title: gpgme_key_t: expired not set on an expired key retrieved from a vali=
dating keylisting
topic: GPGME
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue112>
______________________________________________________

["expired-cert.pem" (application/octet-stream)]

_______________________________________________
Gpa-dev mailing list
Gpa-dev@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gpa-dev


[prev in list] [next in list] [prev in thread] [next in thread]