Page MenuHome GnuPG

Kleopatra: Remove "in n days/weeks/months/years" input from Change Validity Period dialog
Testing, NormalPublic

Description

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.

Event Timeline

werner triaged this task as Normal priority.Jul 28 2023, 10:08 AM
werner added a project: kleopatra.
werner added a subscriber: werner.

I agree.

ikloecker added a project: Restricted Project.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker changed the task status from Open to Testing.Jul 28 2023, 12:57 PM
ikloecker removed ikloecker as the assignee of this task.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

Done.

I have also further unified the handling of the expiration date when

  • generating a new OpenPGP certificate
  • changing the validity period of an OpenPGP certificate
  • certifying an OpenPGP certificate

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.