Bug 805026 - libssh2 fails key re-exchange when write channel is saturated
Summary: libssh2 fails key re-exchange when write channel is saturated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libssh2
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 804145
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 13:27 UTC by RHEL Program Management
Modified: 2012-03-28 09:26 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When sending a large amount of data over SSH, libssh2 could, under certain circumstances, fail to resume an interrupted key exchange. Instead of that, further data was erroneously sent, which caused the remote site to close the connection immediately. This update modifies the code of libssh2 so that libssh2 now properly resumes the interrupted key exchange before sending any further data. The connection remains open and the data transfer proceeds as expected.
Clone Of:
Environment:
Last Closed: 2012-03-28 09:26:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0431 0 normal SHIPPED_LIVE libssh2 bug fix update 2012-03-28 13:25:03 UTC

Description RHEL Program Management 2012-03-20 13:27:29 UTC 
This bug has been copied from bug #804145 and has been proposed
to be backported to 6.2 z-stream (EUS).
Comment 7 Miroslav Svoboda 2012-03-21 13:35:26 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When sending a large amount of data over SSH, libssh2 could, under certain circumstances, fail to resume an interrupted key exchange. Instead of that, further data was erroneously sent, which caused the remote site to close the connection immediately. This update modifies the code of libssh2 so that libssh2 now properly resumes the interrupted key exchange before sending any further data. The connection remains open and the data transfer proceeds as expected.
Comment 13 errata-xmlrpc 2012-03-28 09:26:13 UTC 
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-2012-0431.html
Note You need to log in before you can comment on or make changes to this bug.