[dependenttypes]

https://eprint.iacr.org/2017/627.pdf

[upofadown]

The current version of libgcrypt is not practically exploitable using the technique described in that 3 year old paper.

[dependenttypes]

I remember that their changes <https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=c... were still variable time and thus able to leak secrets. I presume that nobody bothered exploiting yet.

Anyway, even if this was fixed (which I doubt it) the point is that they had vulnerable code for 18 years.