KEYPAIRINFO in 2.2 lacks the algorithm (and the fingerprint time). Kleopatra uses the algorithm to check if the algorithm is allowed in VSD.

115.3.1esr

Yes, there is clearly a problem with the handling of NDEF. I have a fix for that but there are other oddities in that pkcs12 object. Do you have the Firefox version you used to create this?

Well, neither OpenPGP certifcate nor CSR creation from a key on a card is offered for any of the cards I tried.
But that is not only for RSA2048, but for all types of keys.

The changes are best reviewed by a developer to check that I didn't make a mistake when I replaced usage of the canSign, canEncrypt, etc. methods with the new hasSign, hasEncrypt, etc. methods or the corresponding compatibility helpers keyHasSign, etc..

The API that you quote at the end is indeed what is comonly understood as how a KEM functions and is exactly what fits to ML-KEM.

It isn't a duplicate. See T6325#176719.

This task is about the creation of OpenPGP certificates or S/MIME CSR from existing card keys. In particular, it isn't about the creation of card keys.

This is probably a duplicate of T6325

works

related to T6325

For Yubikey it looks the same for me, the CSRs creation buttons are always greyed out (checked for RSA 2048, 3072, brainpool)

On Yubikey and OpenPGP card, OpenPGP creation is possible for RSA2048, too.
Key creation on Yubikey with Curve25519 fails with "General error", it is not disabled in Kleo.
On the Zeitcontrol OpenPGP card it is not offered (but it does not have the capability, anyway, AFAIK)

As I have installed several test versions on Windows since and did never notice a self test during usage, this obviously works

TeleSec NetKey v3 cards are accepted, for NetKey v2 you get the error message "NetKey v2 cards are not supported".

Please send us patches (to this branch).

One question on the future cooperation: is it from now on possible to directly commit to these branches or will we continue to work with uploading patches to this task?