This has a serious usability issue. If you cancel the password entry when exporting it reports success and creates an apparently valid secret key file but without the subkey you intended to export. So worst case the user thinks he has a backup but instead has no backup :/

works

works as described by Ingo

What is a partial CRL; I have never seen that and IIRC the specification for that was not complete.

For what it is worth, I think that my patch is more standard compliant then yours because it checks if there is a partial CRL.

I think 289fbc550d18a7f9b26c794a2409ba820811f6b3 implemented this wish from 2016 :) @werner please read the full report and then close it as fixed if you agree. I find it a bit funny that we both came independently to the same conclusion, that it should be handled differently even if the standard says otherwise. Because the behavior from the standard does not make sense and is in contradiction to other parts where it says that each CRL must contain all revocations.

As part of this the "Change Reset Code" button should be hidden in the general user interface.

This is about showing the corresponding about dialog text for the disable support option.

The default validity period can be specified in the configuration file with

[CertificateCreationWizard]
ValidityPeriodInDays=42

Quick gen key is only used for the keygen in GpgOL and KMail. Kleopatra itself uses the old batch generate interface.

--quick-gen-key supports this but there is no general option; the 2 years are hard coded.

This works with the message class changing. We still need to do it for OpenPGP, too.