Kleopatra: Changing expiry does not change expiry for subkeys
Testing, NormalPublic


Reported in wald: https://wald.intevation.org/forum/message.php?msg_id=6777

Kleopatra apparently only changes the expiry on the primary key. There should be at least an option or a question to change the expiry also for subkeys.

aheinecke created this task.Oct 3 2019, 3:29 PM
aheinecke reassigned this task from aheinecke to ikloecker.Jul 27 2020, 2:57 PM

In Kleopatra/src/dialogs/subkeyswidget.cpp there is already a context menu for subkeys.

This should now have the option to change the expiry date. Alternatively we could make the expiry editable in the list. But I don't know how to do this easily with a nice interface.

So IMO it should be OK to do a right click on the subkey. If its a secret key then offer the option to change expiry, which will then bring up a datetime picker with the current expiry date preselected. There already is an expirydialog in kleopatra.

I don't think we need the full logic of a job / command like the current expiry stuff. When the expirydialog is accepted it can start the sync call to gpgme_set_expire in the background and either show an error when finished or update the key in the subkeyswidget to reflect the changed dates.

ikloecker changed the task status from Open to Testing.Aug 12 2020, 12:30 PM
ikloecker reassigned this task from ikloecker to aheinecke.
ikloecker added a subscriber: ikloecker.

The expiry of the subkeys (and that of the primary key) can now be changed via a context menu action in the subkeyswidget.