Private key shows up as expired (SHA-1 hash)
Categories
(MailNews Core :: Security: OpenPGP, defect)
Tracking
(Not tracked)
People
(Reporter: tobias.bengfort, Unassigned)
Details
Steps to reproduce:
I have a private key that is set to never expire.
Actual results:
Since the update from thunderbird 91.7.0 to 91.8.0 the key shows up as expired since 2019-04-25. It can no longer be used to encrypt messages. When I try to change the expiration date I get the message "This is a key with a complex structure, changing its expiry date isn’t supported."
Expected results:
The key be usable as it is not expired.
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
This is likely related to our update that will reject self-signatures on a key that involve the use of SHA-1 algorithm, which is considered insecure.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 2•2 years ago
|
||
Thanks for the quick response. I used refreshed the expiration information using gpg --edit-key and re-imported it into thunderbird. Now everything is back to normal.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Do you know which software you originally used to extend the key's validity? (I'm not asking about your action on 2022-04-12, but about the action in the past, probably you did that in 2019.)
If it was GnuPG, can you please say what version of GnuPG you likely had used?
Reporter | ||
Comment 5•2 years ago
|
||
Pretty sure it was enigmail. I cannot say which version though.
Description
•