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.
Mon, Apr 19
Thu, Apr 15
Making this task up to HIGH priority, so that people can easily find this change in 2.3.0.
Tue, Apr 13
Done in 2.3.0.
Done in 2.3.0.
Done in 2.3.
Mon, Apr 12
Mon, Mar 29
Sorry to dig up an old report...
Fri, Mar 26
Looks good to me, it no longer returns immediately with the error when there are no readers and the command itself seems to work. Thanks.
Ah, I see that when there is no card reader, it returns "Service is not running" with PC/SC.
Let's fix that.
Thu, Mar 25
When testing under Windows "scd devinfo --watch" returns immediately with ERR 100663614 Service is not running <SCD>
Probably also if you would use PC/SC on Linux but I have not tested this.
Mar 16 2021
Mar 12 2021
More than a year in testing, and I have not seen problems myself anymore.
Feb 17 2021
Feb 12 2021
Feb 10 2021
Works for me.
Feb 8 2021
Thanks for the fix.
Feb 5 2021
pubkey_cmp should be symmetric (pubkey_cmp(A,B) == - pubkey_cmp(B,A)), but it was not.
Feb 3 2021
The problem persists when using keyboxd which returns keys in a different order.
Jan 29 2021
Jan 28 2021
Jan 27 2021
https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man2/posix_spawn.2.html dated August 9, 2007.
So, I guess that posix_spawn became available in MacOS X Leopard (10.5).
Also support older MacOS X, which has no posix_spawn.
Jan 26 2021
T4702 is our release info task for 2.3.0
@gniibe Hi! Can you estimate, when this feature will be released?
I have not found this patch in the latest GnuPG release tags (in the Git repository) either by the name or the commit hash.
Jan 23 2021
Jan 20 2021
Do you mean self-signed certs or what kind of certs do not work?
Jan 19 2021
For a bug which requires more tests (like this one with GnuPG and pinentry), I had a practice to put "Testing" tag.
Jan 18 2021
Any news about this bug? It has been in “Testing” for quite a while now. For what it’s worth, handling of ^C seems to work here as I would expect, so I am inclined to close here and let pinentry-1.1.1 go out. @gniibe, as you did the fix, do you have any comment?
Jan 7 2021
gcry_ecc_get_algo_keylen has been added with commit a658c9ccc2c741f40b0b5cdbcd184cfb9a841d17 but documentation is missing.
Jan 5 2021
I think we can close this one, right?
Jan 2 2021
Hi there, this change is very useful on the Homebrew project's upcoming ARM port. The Mac package manager's base library prefix will change from the existing presumed defaults to prevent backwards-incompatibility, making pkg-config compatibility somewhat more important.
Dec 25 2020
Dec 14 2020
Thank you for testing.
For the issue #1, I think it is the probelm of rG1cd615afe301: gpg,card: Allow no version information of Yubikey.. This was introduced by the support of PIV feature of Yubikey.
Thank you for testing.
For the issue #1, I think it is the probelm of rG1cd615afe301: gpg,card: Allow no version information of Yubikey., which is fixed already. This was introduced by the support of PIV feature of Yubikey.
Dec 12 2020
Report on some testing using master:
Dec 9 2020
This works now. Thanks.
Dec 7 2020
We need another patch, because there are two places for gpg --card-edit and gpg-card to check OpenPGPcard's version number if it's >= 2 or not.
Dec 4 2020
if I am running master, it is now possible to have a setup where the same encryption key is shared by and usable from multiple smart cards?
Thank you for all the work! Does it mean that, if I am running master, it is now possible to have a setup where the same encryption key is shared by and usable from multiple smart cards?
Dec 3 2020
I think that T5150 was also not fixed completely.
So, I'm going to push D513 to both of 1.8 and master (to be 1.9).
Nov 30 2020
Works now. Thanks.
Nov 27 2020
Nov 26 2020
Sorry, I realized this myself this morning and did couple of fixes. rG7113263a00d8 does this all however I forgot to mention the bug number.
Argh. The following patch replaces the previous patch. It fixes the calculation of the display serial number.
I think the calculation of the OpenPGP s/n is not correct. As you write, "Yubico seems to use the decimalized version of their S/N as the OpenPGP card S/N." This matches my observation for my Yubikey:
s/n printed on Yubikey: 9074582
Yubikey s/n (with our prefix): FF020001008A7796
OpenPGP AID: D2760001240102010006090745820000
Nov 25 2020
Great. Please apply the patch.
Nov 24 2020
Okay, I now got such a patch:
I found a good enough solution: I changed the code to compute the OpenPGP s/n from the Yubikey s/n right after a Yubikey has been detected. Later, and if OpenPGP enabled on the YK, the S/N is already there but we use the S/N from the 0x4f DO. That is needed because we can't compute the OpenPGP version number ahead and use 0.0 in the S/N.
Stable now and works as expected. Thank you!
Nov 23 2020
Its done for 2.2 thus changing the tag.