Open Bug 1687982 Opened 5 years ago Updated 5 years ago

PGP keys those expiration date has been changed are still considered as expired in the key manager

Categories

(MailNews Core :: Security: OpenPGP, defect)

Product:
MailNews Core
Component:
Security: OpenPGP
Type:
defect

Tracking

(Not tracked)

Status:
UNCONFIRMED

People

(Reporter: nathan.passeron, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

The public key of a colleague expired. So I couldn't send him a ciphered email. Then he changed the expiration date with an external key manager (Kleopatra). After re-importation of his key, it's still considered as expired.

So to reproduce:

  1. create a public key that expired just after its creation
  2. import it in the key manager: open the key manager -> file -> import key from file -> choose the file holding the key previously created (so need to export it with the external key manager)
  3. change the expiration date of the created key (the same key, do not create a new one) so that it's not expired anymore
  4. re-import it

Actual results:

After re-importation the key is still expired. Impossible to send a ciphered email with it.

Expected results:

The key should be valid and usable.

Component: Mail Window Front End → Security: OpenPGP
Product: Thunderbird → MailNews Core
You need to log in before you can comment on or make changes to this bug.