Most things are done. Missing stuff

Alright: We have support for all our combined algos ky{768,1024}_bp{256,384,512}and ky{768,1024}_cv{25519,448} as well as test keys and encrypted test messages.

What is the current status of this issue?

Here comes a new test key along with its 3 secret parts (one for the primary and two for the composite Kyber subkey).

Wit the test keys posted in T7014 it is now possible to decrypt the sample data. The test data has been slightly adjusted for the new format; see

See also: https://gnupg.org/blog/20240125-smartcard-backup-key.html

Also fixed in the fortgcoming 2.2.43

Fixed in 2.4.4. Feel free to re-open if you still see problems.

Fixed in 2.4.4 and 2.2.43 - see above for affected versions.

We need to fix 2.2.42 too. This because we backported the responsible patch.

We tested with Kleopatra:

• Only gpg4win 4.2 is affected (the current version) but 4.1 is not affected.
• No vsd version is affected.

FWIW, I am already working on this.

Currently, there is no support for gpg-agent to keep private key not on disk, but only on memory of gpg-agent. Given the situation,
I think that it is good to:

Way to late for a change and also adding another algorithm (SIV) complicates things for no good purposes.

I applied your patch and also fixed another possible problem.

It's true that for KEYTOCARD command, there is optional argument for ECDH.
My point is that for PKDECRYPT command, it will be needed to add mechanism for getting such a parameter (when we use KEM API in gpg-agent).

We already have the ECDH parameters for OpenPGP in the gpg-agent API. The question is how large the data for PQC will be - likely we need to use an inquire already for this reason.

Considering the design of gpg-agent which focuses on private key operations and data, it would be better to enhance the gpg-agent protocol to inquire public key data of any format defined by the client (including ECDH KDF parameters of OpenPGP). I mean, instead of storing data in the key file (originally designed for private key + some additional data), we will enhance the protocol.

Further investigation showed that this was due to a bogus key creating during I wrote the code.

Will be in 2.4.4. GPGME 1.23.0 with support has been released.

While trying to replicate your findings I might have found a but in the import code which rejected one of the keys (using gnupg 2.2). I'll take care of this.

@ebo: Du have the Ted Tester key (i.e. the ADSK key) also in you keyring?

Encryption to the ADSK seems to work but I'm not sure if everything is displayed as expected.

works