Page MenuHome GnuPG

Kleopatra: Offer only compliant algorithms for key generation on smart cards in VSD
Closed, ResolvedPublic

Description

In VSD we do not want to offer key generation with non compliant algorithms.
At the moment the following are offered for Yubikeys (as an example):

As RSA 2048 will no longer be allowed from 2023-01-01 on, we should no longer show that. And not Curve 25519 either, which is currently not approved.

Details

Version
VS-Desktop-3.2.0.0-beta229/231

Event Timeline

Choosing Curve 25519 results in a general error btw.

This is probably a duplicate of T6325

aheinecke added a subscriber: aheinecke.

I tend to give this high priority since our SecOps state that the creation of non vs-nfd compliant keys is inhibited by our software by default (at least in the UI) I mean no one complained and it is not a regression but this should be fixed soonish. But this does not neccessarily mean before the next release.

ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker renamed this task from Kleopatra: do not offer all possible algorithms for key generation on smart cards in VSD to Kleopatra: Offer only compliant algorithms for key generation on smart cards in VSD.Oct 23 2023, 12:27 PM
ikloecker changed the task status from Open to Testing.Oct 25 2023, 11:48 AM
ikloecker removed ikloecker as the assignee of this task.

Only compliant algorithms are offered when (re)generating single keys or all keys. In de-vs mode, Brainpool 256 is preselected if the smart card supports it. Otherwise, RSA 3072 is preselected.

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Oct 30 2023, 4:06 PM
ikloecker moved this task from Backlog to WiP on the vsd32 board.
ebo claimed this task.
ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

works

ebo edited projects, added vsd32 (vsd-3.2.0); removed vsd32.