Bug#699034: Is this fixed in upstream LIBGCRYPT-1-5-BRANCH?

[Andreas Metzler]

On 2013-02-24 Trek <trek00 at inbox.ru> wrote:
> On Sun, 24 Feb 2013 16:34:32 +0100
> Andreas Metzler <ametzler at downhill.at.eu.org> wrote:

> >relevant patches. Could you please test whether
> >http://people.debian.org/~ametzler/libgcrypt11_1.5.0-3+test+2_i386.deb
> >also does the trick? It just adds three patches
> >(35_Avoid-dereferencing-pointer-right-after-the-end.patch
> >39_Fix-segv-with-AES-NI-on-some-platforms.patch
> >40_libgcrypt-1.5-rinjdael-Fix-use-of-SSE2-outside-USE_A.patch) instead
> >of 11.

> It runs fine and the bug no longer shows up. I can exclude also the
> patches 39 and 40 as the CPU is an old AMD Athlon without AES-NI and
> SSE2.

Hello,
I actually think 40 is the culprit, it is about invoking SS2 on non-AESNI
(even if they do not support SSE2) which according to the commit
messages causes "crashes later on". This matches perfectly with the
bug diagnosis "memory corruption".

As the other two patches are short and also fix at least important bug
I will also keep them.

thanks again, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'