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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 10 2023
I think ".UTF8" is always better than LC_TIME="" if the display string contains non-English Unicode chars.
Oct 9 2023
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?
Oct 8 2023
Oct 7 2023
Merged to master for 23.12 as it includes new UI and translations strings.
Both PR merged into master, fix will be in 23.12 (the fix required cross-library API changes)
Oct 6 2023
With current VS-Desktop-3.2.0.0-beta229/231 this does not work for me. Neither for RSA 2048 nor 3072.
The CSR buttons are greyed out
Choosing Curve 25519 results in a general error btw.
works, either name or email is enough
fwiw: For a Netkey 3.0 card with expired RSA 2048 certificates, CSR creation is not offered.
❯ /opt/local/bin/gpg-error 100696144 # installed with MacPorts 100696144 = (6, 32848) = (GPG_ERR_SOURCE_SCD, GPG_ERR_ENODEV) = (SCD, Operation not supported by device)
I am wondering a bit about the gpg: DBG: chan_3 <- ERR 100696144 Operation not supported by device <SCD> which is not the string I expected for this error:
With the above changes a group with an expired key is now expanded. But, as in T6742, the key is shown with the blue info icon instead of with a red X icon and the OK button is enabled.
Pushed the change into kem-kyber branch.
https://dev.gnupg.org/source/libgcrypt/history/kem-kyber/