Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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):
libssh2-1.2.2-7
How reproducible:
Run the provided script
Steps to Reproduce:
1. Install Net::SSH2 (e.g. via CPAN)
2. Run the provided perl script
Actual results:
LIBSSH2_ERROR_EAGAIN
Unable to exchange encryption keys
Net::SSH2::DESTROY object 0x20474b0
Expected results:
no LIBSSH2_ERROR_EAGAIN
Additional info:
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
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
release.
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.
http://rhn.redhat.com/errata/RHBA-2013-0329.html