Page MenuHome GnuPG

GpgOL: RSA 2048 Key generated in VSD
Closed, ResolvedPublic

Description

Noticed when testing T6683:
After acknowledging the new "No X509 certificate found" window and choosing in the next window -> OpenPGP -> Generate, a "generate key, this may take a while"- window appears and does not go away (at least not in the usual time...) although in the background the newly generated key is listed in the certificate list in Kleopatra.
After hitting cancel on 2 windows checking the details of the generated key show that it is RSA 2048.
But it is shown as VS-NfD compliant anyway.

When trying to send a signed mail the next time, this certificate is used and accepted as compliant.

Details

Version
VS-Desktop-3.1.90.267-Beta

Event Timeline

ebo triaged this task as High priority.Nov 9 2023, 1:58 PM
ebo created this task.

We consider rsa2048 as compliant until the end of this year; this is required due to the Telesec smartcards. However, we should never create such a key and kleopatra does not allow this.

This is an incarnation of T6685 while we decided to deprecate that job we did not open a ticket to do it and forgot about it. So we did not notice that it was still used in the keyapprovaldialog. Fix is to replace it there with the correct key generation job.

libkleo/src/ui/newkeyapprovaldialog.cpp

ikloecker changed the task status from Open to Testing.Nov 10 2023, 2:28 PM
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

We are now generating a key with whatever defaults gpg uses.

That sounds very good.

ikloecker mentioned this in Unknown Object (Event).Nov 13 2023, 9:10 AM
aheinecke moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Nov 13 2023, 9:12 AM

With VS-Desktop-3.1.90.277-Beta the generated key is the default RSA 3072.

But the part with the "key generation" window not closing remains. I aborted the "key generation" (which at this point was long done) after 5 minutes. Do you want a new ticket for that or do we continue here?

No it is just not properly selected after generation but it is there. I think there might even be an issue for that already. But definitely not something related to vsd 3.2

The issue for that is: https://dev.gnupg.org/T6566 so I think this can be resolved here?

After reading the initial description of this, I think that might even be a yet a different bug. For which we then would not yet have a ticket. :)

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

Ok closing, remaining issue is in T6813

ebo edited projects, added vsd32 (vsd-3.2.0); removed vsd32.
ebo moved this task from Backlog to gpgme 1.23.x on the gpgme board.
ebo edited projects, added gpgme (gpgme 1.23.x); removed gpgme.
ebo moved this task from gpgme 1.23.x to QA for next release on the gpgme board.
ebo edited projects, added gpgme; removed gpgme (gpgme 1.23.x).