Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1602799 - aes192-ctr and aes256-ctr ciphers not supported
Summary: aes192-ctr and aes256-ctr ciphers not supported
Keywords:
Status: CLOSED DUPLICATE of bug 1592784
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libssh2
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-18 14:16 UTC by Fred Gleason
Modified: 2018-07-19 15:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-19 15:40:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Fred Gleason 2018-07-18 14:16:16 UTC
Description of problem: The current version of libssh2 (v1.4.3-10) does not support the aes192-ctr and aes256-ctr ciphers. This means that, with the deprecation of aes128-ctr, no secure ciphers are available and connections fail to sites offering only aes192-ctr and aes256-ctr.


Version-Release number of selected component (if applicable): 1.4.3-10


How reproducible: Always


Steps to Reproduce:
Use curl (which uses the libssh2 library) to attempt an SFTP transfer to a hardened site:

*** snip snip ***
[fredg@elastigirl temp]$ curl -v -k -u [REDACTED]:[REDACTED] -T tone.mp3 sftp://radioamerica.wpengine.com:2222/on-air-with-doug-jen-and-victoria/ARCHIVE/tone.mp3
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* About to connect() to radioamerica.wpengine.com port 2222 (#0)
* Trying 104.197.62.172...
* Connected to radioamerica.wpengine.com (104.197.62.172) port 2222 (#0)
* Failure establishing ssh session
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
* Closing connection 0
curl: (2) Failure establishing ssh session
*** snip snip ***


Actual results: Session fails


Expected results: Session succeeds


Additional info: As a short-term fix, upgrading libssh2 to the most recent upstream version (v1.8.0) corrects the problem.

Comment 2 Kamil Dudka 2018-07-19 15:40:22 UTC
We already have an internal bug requesting a rebase of libssh2 in RHEL-7 to 1.8.0.

While it is technically possible, it comes with a risk of regressions.  Generally, we try to avoid rebases of packages in already released enterprise products whenever possible.

If you are a customer of Red Hat, please contact Product Support.

*** This bug has been marked as a duplicate of bug 1592784 ***


Note You need to log in before you can comment on or make changes to this bug.