Backport was done with commit rC1d312bc65846 (for unknown reasons it did not show up in the list of bugs related to this bug; I added it by hand). Fix will go into 1.8.8.
Mon, Apr 19
Feb 17 2021
Feb 1 2021
I think that a backport to 1.8. also makes sense
Jan 28 2021
Jan 18 2021
Dec 11 2020
Reading the code again, I think that some configuration of NKS card doesn't work well, when it has no certificates but keys (e.g. IDLM config).
I'm going to fix do_readkey as well (the approach #1).
Dec 10 2020
With little (mostly no) knowledge of NKS card, I think I fixed this issue.
Thanks a lot for your time to locate the problem. I took the approach of #2.
Dec 9 2020
I'm not sure why I thought that it would work now. With current master I get
$ gpg-connect-agent "SCD READKEY --info-only -- 39400430E38BB96F105B740A7119FE113578B59D" /bye ERR 100663414 Invalid ID <SCD>
Dec 3 2020
Fixed in master. I will backport to 2.2.
Nov 30 2020
Seems to work now. I'm not sure whether I should close this issue because it's marked for backport.
Nov 27 2020
Regarding a backport I think that I will eventually backport all app-*c to stable by source copying them. We have a quite stable internal API and thus it is easier to keep at least the card specific code in sync. I did some local work in this directory some time ago.
Nov 26 2020
Nov 9 2020
Nov 6 2020
Aug 29 2020
Apr 27 2020
Oct 24 2018
Thanks. May also happen if the first print_assuan_status fails.
Oct 23 2018
Thanks. Fixed in master. Needs backport.
Thanks. Fixed in master.
Oct 8 2018
Editor fault. The browser's editor is not like Emacs and here o my laptop the backspace key does not work as intended. I guess I was about to write ".. a back signature's usage flag".
what does "back signature's usage tool" mean? can we make an addition to the test suite that ensures that bad signatures will be rejected?
The fix was not fully correct because it considered a back signature's usage tool.
Jun 21 2018
Done for master. Needs backport.
Jun 12 2018
thanks for looking into this so quickly. where is your patch? i don't see it on the master branch yet.
Thanks for reporting and your patch. However, I used a different way to solve this bug.
Thanks. Pushed to master. I think it should also go into 2.2.
Jun 9 2018
Jul 17 2017
I just verified that this is indeed fixed.
Jul 3 2017
No I don't recall any such problems, sorry.
Jul 1 2017
Mar 30 2017
Jul 15 2016
Apr 19 2016
Feb 24 2016
I've tested it with pubring now too and it works.
Justus mentioned in jabber that he noticed some more errors after this patch in
the scheme tests. I've not tried them.
Okay, so I can backport this to 2.0 ?
Feb 22 2016
Tested this with keybox and it appears to be working. When running a keylist
while importing the import holds for a bit and continues after the keylist.
Not tested this with keyring yet.
Jan 15 2016
Jan 5 2016
Commit e70f7a5 fixes this for 2.1.
Should be backported.
Dec 17 2015
backported by dkg with commit 0c3d764 for 1.4.19
Nov 20 2015
dkg: I've now applied your backport to the 1.4 branch. Sorry for not doing this
sooner. I believe that this now completely rectifies this issue. As such, I'm
marking this issue as resolve. Thanks.
Nov 18 2015
Based on Werner's comment, this issue has been addressed. As such, I'm closing
this bug report.
Sep 22 2015
See T2106 for the SHA-256 feature.
I have not yet used that new ssh version. Will look into it soon to get the MD5
The MD5 bug has been fixed with commit 2167951:
- gcry_md_write (md, "384\0\0\0\x08nistp521", 15);
+ gcry_md_write (md, "384\0\0\0\x08nistp384", 15);
Sep 8 2015
2.0.29-beta has a fix for this. See also T1823.
backport for 2.0 commited. Thanks.
Jun 30 2015
Feb 18 2015
Fixed with commit 0c3d764.
Should be backported to 1.4.
Feb 12 2015
Back ported to 2.0 (commit 2b2adb85948ce2c7db727ebc0c99e8ad2c29bf5f)
Jan 28 2015
Fixed for 2.1 with 382ba4b.Should be backported to 2.0 and 1.4.
Jan 26 2015
Should be fixed by commit 017c6f8fba9ae141a46084d6961ba60c4230f97a
Backported to 2.0: commit 2424028.
Nov 24 2014
backported to 2.0 and 1.4.
Nov 17 2014
Fixed in master will be backported to 2.0.
That is a very well written bug report. Thanks.
Sep 17 2014
Jun 23 2014
Backported to 1.4. It has also been applied to master some time ago.
Jun 2 2014
Fixed for master.
Fixed for 2.0. But take care: The code now also uses the fixed-list-mode which
is the default in --list-keys for ages:
uid:::::::::George Hacker <firstname.lastname@example.org>:
uid:::::::::George Hacker <email@example.com>:
uid:::::::::George Hacker (GLS) <firstname.lastname@example.org>:
Jan 30 2014
Jan 29 2014
Thanks, it's no problem to wait until 1.6.2. I just tested the patch and it's
working as intended.
I recall that I looked up the commit id this morning but obviously was disturbed
and thus didn't actually complete the cherry-pick. Sorry. I just pushed the
change. We need to wait some time before we can do a 1.6.2.
I attach a patch for 1.6.1.
Did you intend to include the changes in 1.6.1? It doesn't appear that they made
it into the release.
Done and 1.6.1 released
Jan 28 2014
Thanks. I backport it tomorrow.
I just tested with the changes applied to the LIBGCRYPT-1-6-BRANCH head, minus
the sha1.c changes (since the NEON parts weren't there), and it is building and
running fine for me. I assume it should work fine in master given this, and can
test that later if you would like, I'm just currently missing the libgpg-error >=
1.13 dependency for doing that. Thanks for your help getting this fixed up.