For the T2238, it was backported in effect (not intentional, though).

1.4: ca1fc59
2.0: 1c15136

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 ?

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.

Commit e70f7a5 fixes this for 2.1.
Should be backported.
Thanks.

backported by dkg with commit 0c3d764 for 1.4.19

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.

Based on Werner's comment, this issue has been addressed. As such, I'm closing
this bug report.

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
fingerprints replaced.

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);

2.0.29-beta has a fix for this. See also T1823.

backport for 2.0 commited. Thanks.

Fixed with commit 0c3d764.
Should be backported to 1.4.

Back ported to 2.0 (commit 2b2adb85948ce2c7db727ebc0c99e8ad2c29bf5f)

Fixed for 2.1 with 382ba4b.Should be backported to 2.0 and 1.4.

Should be fixed by commit 017c6f8fba9ae141a46084d6961ba60c4230f97a
on 2014-06-24.

Backported to 2.0: commit 2424028.

backported to 2.0 and 1.4.

Fixed in master will be backported to 2.0.
That is a very well written bug report. Thanks.

Backported to 1.4. It has also been applied to master some time ago.

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:

pub:-:1024:17:4713D527ECE16009:1118095577:::-:
fpr:::::::::8BFD3F436366D9820E9EAB2F4713D527ECE16009:
uid:::::::::George Hacker <georgeh@axian.com>:
uid:::::::::George Hacker <ghacker@axian.com>:
uid:::::::::George Hacker (GLS) <ghacker@redhat.com>:
uat:::::::::1 2493:
sub:-:1024:16:0D94CF6C0C8C2F1B:1118095578::::

Thanks, it's no problem to wait until 1.6.2. I just tested the patch and it's
working as intended.

Oh no!

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.

D187: 422_0001-cipher-Take-care-of-ENABLE_NEON_SUPPORT.patch

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

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.

Backported for 1.6.1

Fixed for master with commit cbdc355.

I don't think it makes sense to backport it to 1.5 - it has been this way for so
long. Users of 1.5 should upgrade to 1.6.0.

Done for 2.0

Meanwhile gniibe fixed a lot more bugs and also ported them back to 2.0. Thus I
close this bug.

Backport to 2.0 done (f772757e)

Backport to 1.4. done (cfb193a1).

Also changed for 2.0 - will go into 2.0.18.
Also changed for 1.4.

Fixed in master.

Fixed in 1.4 since 2009-07-23.
Released with 1.4.10.