RFC-5280 states in 4.2.1.3 for Key Usage:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 3 2021
The error code is: No Readers Available. With the latest version you should have seen that string.
Meanwhile we did some more tests on Windows and so you many want to try our betas at
Can you please clarify this point: If you run on Unix with --disable-ccid-driver, do you get the same behavior as on Windows?
Apr 30 2021
Run gpg --debug ipc --card-status to quickly see the communication with the scdaemon.
Apr 29 2021
Apr 28 2021
Please try to verify on the command line (cmd.exe):
Apr 27 2021
The curve is not defined to be used for ECDH (encryption); in fact it should in general only be used with the EdDSA
algorithm. You need to use "Key-Type: eddsa". Note that the EdDSA signing algorithm is different than the commonly used ECDSA signing algorithm.
Can you please port this also to 1.8?
You can't use ecdh with ed25519.
Apr 26 2021
Please install the Gnome Key Ring prompter tool or use the plain GTK pinentry.
Apr 25 2021
Apr 23 2021
Please have a look at the log:
Apr 22 2021
You are right. The problem is that in a development version we use an envvar to locate the programs, so there is usually no problem because the software has already been installed and the final test doesn't catch this. We should add a version check to all components to catch such problems.
Given that we don't yet support TPM for Windows you should go ahead and apply this patch. tpm should also be removed from the list of components.
Apr 21 2021
6f03 = Data with specified length not supported.
Needs to be fixed in GnuPG :-(
Apr 20 2021
is more important
Apr 19 2021
You can't use an EdDSA as subkey for encryption. Encryption is the default for a subkey unless you provide key usage parameters. Yes, we could flag this as an error, but I won't give it high priority. I would anyway suggest to use
Thanks, that was right in time for this weeks 2.3.1.
aheinecke: I agree, we should not port everything back just because we could do that.
Has been released with 2.3.0 and we better open a new task if problems show up with v5 key. I am pretty sure that there will be a few v5 key problems after they get in real use.
This has been released with 2.3.0 and no relevant problems have reported in the last two weeks, thus closing.
Apr 18 2021
t-link does not do antthing useful, anyway. I don't think it is justified to add dlopen stuff. Running real test is anyway a manual action; for a full test automation we would need to emulate all supported cards.