Description of problem:
libssh2 returns LIBSSH2_ERROR_EAGAIN in blocking mode when trying to connect with a Perl script using Net::SSH2
Version-Release number of selected component (if applicable):
Run the provided script
Steps to Reproduce:
1. Install Net::SSH2 (e.g. via CPAN)
2. Run the provided perl script
Unable to exchange encryption keys
Net::SSH2::DESTROY object 0x20474b0
Weird enough the script still works when one would remove the error handling from the connect() call. So even after returning the EAGAIN, the other library calls work fine (auth_publickey(), scp_put()). The script works without flaws on libssh2-1.2.7. Just removing the error handling after connect or ignoring the EAGAIN is not an option as this would affect too many scripts from a 3rd party software, so this is not suitable as a workaround.
I did try to enable tracing but was not able to gather more information from the traces. They're attached.
Created attachment 587702 [details]
successful run with libssh2-1.2.7
this is a trace of libssh2 and the output of the script from a successful run with libssh2-1.2.7
Created attachment 587703 [details]
unsuccessful attempt with libsssh2-1.2.2
this is a trace of libssh2 and the output of the script failing with libssh2-1.2.2
Created attachment 587704 [details]
Net::SSH2 test script
Thanks for the reproducer. git-bisect points to this upstream commit as the fix:
I will need to check whether the fix is applicable on RHEL-6 libssh2 on its own.
Created attachment 587718 [details]
backport of upstream commit 697b4e8
The attached one-line patch fixes the issue and does not seem to break anything at first glance. I was able to pass 43 SCP/SFTP tests from rawhide curl against the patched libssh2 library.
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time. It has been proposed for the next
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.