Page MenuHome GnuPG

QGpgME: Update defaultkeygenerationjob and use create-key API
Closed, WontfixPublic


The defaultkeygenerationjob in qgpgme uses outdated defaults and the old API with the parameter file.

Instead it should use the create key API and let GnuPG decide what the defaults are. This is important because nowadays the defaults are configurable e.g. for VSD its 3072 bit RSA while for Gpg4win it is cv25519.

Event Timeline

aheinecke triaged this task as Normal priority.Aug 28 2023, 1:54 PM
aheinecke created this task.

Kleopatra doesn't rely on the defaults in the library and other users shouldn't either. I would kill defaultkeygenerationjob. And it's use in newkeyapprovaldialog should be fixed, e.g. by using QuickJob::startCreate().

Even more shockingly, there's a copy of the job in libkleo.

aheinecke claimed this task.

Nevermind we clarified in chat that we would instead deprecate this API.

Well I guess T6805 is now the followup ticket that I did not create when I just closed this issue as Wontfix. Ingo can you take T6805 and do what you wrote in your last message here?