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:

When transferring really large files with curl scp:// the connection is not closed. This seems to be related to key re-exchange - bugs 804145, 804145.


Version-Release number of selected component (if applicable):
libssh2-1.2.2-7.el6_2.3

How reproducible:
always for me

Steps to Reproduce:

1. To reproduce use the patch openssh in a way mentioned in Bug 804145#c1. The patch is a bit different for RHEL6.2 openssh and has to be "ported", also you can use >>=10 instead of >>=5 to speed up requests for new key.

2. Prepare ssh keys for current user 
3. Execute patched sshd on a different port (or instead of running sshd)

# /path/to/patched/sshd -p 2048 -f /etc/ssh/sshd_config -d &

4. initialte a download of large file (so the keys are re-exchanged during the download, can be seen in sshd debug messages)

$ curl -v -u username: --key ~/.ssh/id_rsa --pubkey ~/.ssh/id_rsa.pub
scp://127.0.0.1:2048/tmp/file -o /dev/null

The bug can be reproduced when transferring from localhost, not from other host
(for me).

  
Actual results:
connection not closed when the file is transferred

Expected results:
connection is closed

Additional info:

without the patched openssh, I believe the bug might appear when transferring files much larger > 64 GB. Doesn't occur for smaller files.

upstream commit:

http://git.libssh2.org/?p=libssh2.git;a=commitdiff;h=03ca902

fixing the typo in bz summary.

This thread seems to be also related:

http://thread.gmane.org/gmane.network.ssh.libssh2.devel/5699/focus=5701

This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a 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