Hide Forgot
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