In the "change validity" dialog "valid until" suggests either the current expiry date of a key or the current date (if the key is already expired or has no expiry date yet).
To make key extension into a 1-click option, a reasonable date should be suggested.
Please change the value to current date + default expiry period. For currently expired keys it should follow that rule, too.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA4c1de4fa434f Propose same expiry as for new certificates when changing validity | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T6553 Kleopatra: Expiry date issues and improvements | ||
| Resolved | • ebo | T6479 Kleopatra: "change validity" dialog shows unreasonable default for extension |
The current date should be avoided even if explicitly chosen, on the command line the earliest allowed date is tomorrow.
The proposed new expiration date is now the same as for the generation of new certificates, i.e. today + configured default validity.
Note: If the default validity is shorter than the remaining validity of a key, then Kleopatra still proposes the earlier end of validity.