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.
Bug 1547144 - openwsmand does not support ECDH ciphers
Summary: openwsmand does not support ECDH ciphers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openwsman
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vitezslav Crhonek
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 1549619 1551541
TreeView+ depends on / blocked
 
Reported: 2018-02-20 15:38 UTC by Alois Mahdal
Modified: 2018-10-30 11:09 UTC (History)
2 users (show)

Fixed In Version: openwsman-2.6.3-4.git4391e5c.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:09:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3200 0 None None None 2018-10-30 11:09:16 UTC

Description Alois Mahdal 2018-02-20 15:38:35 UTC 
Description of problem
======================

While testing bug 1454607 (to enable cipher blacklist), it turned out
that openwsmand does not handle ECDH properly.  That is, if I set cipher
list to eg. ECDH (ie. all ECDH based ciphers), s_client with DEFAULT
set will not be able to connect.

According to @hkario, this could be caused by misconfiguration on
openwsmand part, since ECDH ciphers may require special configuration
calls (which indeed don't appear in downstream shttpd.c).



Version-Release number of selected component
============================================

openwsman-server-2.6.3-3.git4391e5c.el7


How reproducible
================

Always


Steps to Reproduce
==================

 1. set ssl_ciphers_list = ECDH
 2. start up openwsmand
 3. connect with a client with ECDH cipher string, eg.

        openssl s_client -connect $SrvHost:$SrvPort -ciphers ECDH <.


Actual results
==============

SSL handshake failure


Expected results
================

Successful connection (or other failure)


Additional info
===============

Alternatively, you can scan openwsmand port with

    nmap -sV --script ssl-enum-ciphers $SrvHost -p $SrvPort

which will reveal that no ciphers were enabled on the server.

Also this is probably not just ECDH but also other EC* ciphers.
Comment 2 Vitezslav Crhonek 2018-02-28 11:58:42 UTC 
https://github.com/Openwsman/openwsman/pull/103

resolves the issue.
Comment 8 errata-xmlrpc 2018-10-30 11:09:08 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.

https://access.redhat.com/errata/RHBA-2018:3200
Note You need to log in before you can comment on or make changes to this bug.