Neither the certificate generation dialog nor the certification dialog offer this additional method for specifying the expiration date. The calendar popup of the date combo box allows to add some useful values like "1 year", "2 years", etc., which I think is sufficient.
Nobody wants to extend the lifetime of their certificate for 314 days or 42 weeks or 7 months. :-)
And if somebody wants this, then they can calculate the actual date with Excel or use gpg directly.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAec9bd48365c5 Remove obsolete functions | |||
| rKLEOPATRAfb8d970115ac Check for valid expiration date when creating new OpenPGP certificate | |||
| rKLEOPATRAd6ab68abf97e Unify setup of expiration date selection | |||
| rKLEOPATRAc30cedf713aa Do not rely on maximum date of combo box for unlimited validity | |||
| rKLEOPATRA04ba26634573 Use the configured (or hard-coded) validity period also for certifications | |||
| rKLEOPATRA2d42d28c2a4d Unify selection of expiration date in different dialogs | |||
| rW Gpg4win | |||
| rWb29e4c3d4008 Add upstream patches which remove useless "no date" option | |||
Done.
I have also further unified the handling of the expiration date when
This issue should be tested together with T6519: Kleopatra: "change validity" allows to set an expiry date in the past.
Yes I think that can be safely backported to gpg4win/23.07
Especially since it thematically matches our improved expiration date handling in that version.
The choice in the calendar "widget" changed to in 1/2/3 years in all cases. Those options work but the last choice "no date" has no effect.
Tested with VS-Desktop-3.2.0.0-beta214
I have created a merge request for upstream to remove the useless "No date" option:
https://invent.kde.org/frameworks/kwidgetsaddons/-/merge_requests/213
I have added a patch with the changes to gpg4win, so that we do not have to wait for the fixed upstream version.
The backport wasn't done because the gpg4win/23.07 branch is dead (the summer release was cancelled).