In the Digital Signatures -> Sign Document | Select Certificate dialog, revoked and expired keys are listed as available. While the Expiration date is listed, there's no indication of revoked keys. Revoked and expired keys should not be listed at all as they can't be used for signing.
Thorsten Behrens committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=087a90e27b7219e8c1aaa880b39376c94a0dcaae gpg4libre fix tdf#113190 don't show expired/invalid keys It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike reports it fixed, I had issues before with gpgme misbehaving on key attributes; hope the fix works for the majority of users out there.
Verified works for me..
Thorsten Behrens committed a patch related to this issue. It has been pushed to "libreoffice-5-4": http://cgit.freedesktop.org/libreoffice/core/commit/?id=561d25301bf2a04a2cd34f1674a792167cf5f43b&h=libreoffice-5-4 gpg4libre fix tdf#113190 don't show expired/invalid keys It will be available in 5.4.4. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 139485 [details] Screenshot with selection box showing expired certificates. Issue remains for me. (x86 and x64) Version: 5.4.4.2 (x64) Build ID: 2524958677847fb3bb44820e40380acbe820f960 CPU threads: 4; OS: Windows 6.19; UI render: GL; Locale: es-ES (es_ES); Calc: CL Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: es-ES (es_ES); Calc: CL Versión: 6.0.0.3 Id. de compilación: 64a0f66915f38c6217de274f0aa8e15618924765 Subproc. CPU: 4; SO: Windows 10.0; Repres. IU: GL; Configuración regional: es-ES (es_ES); Calc: group
m.a.riosv has expired X.509 keys in Windows, me also. But this issue is titled "OpenPGP". So it's not clear whether this should be reopened or new bug created for X.509.
Looks like there's a consequence of showing expired X.509: we can use it to sign, but nothing really happens.
(In reply to Timur from comment #6) > m.a.riosv has expired X.509 keys in Windows, me also. > But this issue is titled "OpenPGP". > So it's not clear whether this should be reopened or new bug created for > X.509. Yes, that's very likely a different issue - unless those keys come from GPG. Do you or m.a.riosv have gpg4win installed? With X509 keys showing in Kleopatra? If yes, I'll need further infos, if not -> please file a separate bug.
Yes, I have gpg4win installed but X.509 keys from Windows system certificate manager that are shown in LO are not shown in Kleopatra. Kleopatra has just OpenPGP (and CAcert I added for test). I guess that's a ne bug then.