Closed Bug 1764400 Opened 2 years ago Closed 2 years ago

Private key shows up as expired (SHA-1 hash)

Categories

(MailNews Core :: Security: OpenPGP, defect)

Thunderbird 91
x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1763641

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.

Component: Untriaged → Security: OpenPGP
OS: Unspecified → Linux
Product: Thunderbird → MailNews Core
Hardware: Unspecified → x86_64

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.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID

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.

Resolution: INVALID → DUPLICATE
Summary: Private key shows up as expired → Private key shows up as expired (SHA-1 hash)

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?

Pretty sure it was enigmail. I cannot say which version though.

You need to log in before you can comment on or make changes to this bug.