On Sat, Feb 06, 2016 at 07:57:35PM +0100, Dan Fandrich wrote:
> I looked into this and the loop is happening within gcry_mpi_powm due to an
> invalid internal condition. I've brought it to the gcrypt devel mailing list.
> The code calling this is new in libssh2 (commit fc4a969a) but still, gcrypt
> shouldn't be hanging like this.
I reported it to the libgcrypt project and they quickly found the bug
in libgcrypt and came up with a fix. Presumably, the fix will be in the next
release (I guess ver. 1.6.6). It's a longstanding bug (that might only affect
32-bit systems) and it's only triggered in libssh2 starting with ver. 1.7.0. If
someone else runs into this, try upgrading libgcrypt.
Received on 2016-02-23