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 1457524 - Problem parsing formatted cipher list
Summary: Problem parsing formatted cipher list
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tomcatjss
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-31 20:59 UTC by Matthew Harmsen
Modified: 2017-08-01 21:09 UTC (History)
2 users (show)

Fixed In Version: tomcatjss-7.2.1-4.el7
Doc Type: Bug Fix
Doc Text:
Previously the cipher list in server.xml had to be specified in a single long line which made it difficult to manage, for example: <Connector sslRangeCiphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256" /> To improve usability the code has been changed to allow the cipher list to be specified in multiple lines, for example: <Connector sslRangeCiphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256" />
Clone Of:
Environment:
Last Closed: 2017-08-01 21:09:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2079 0 normal SHIPPED_LIVE tomcatjss bug fix and enhancement update 2017-08-01 18:37:21 UTC

Description Matthew Harmsen 2017-05-31 20:59:48 UTC 
In some cases (e.g. in FIPS mode) the admin will need to modify the SSL cipher list in server.xml. Currently the cipher list needs to be specified as a single (and often times long) line without line breaks which makes it difficult to manage and error prone. For example:

<Connector
    sslRangeCiphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256"
    />

To improve usability the cipher list should support the following format:

<Connector
   sslRangeCiphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
       TLS_DHE_RSA_WITH_AES_256_CBC_SHA,
       TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,
       TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,
       TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
       TLS_RSA_WITH_AES_128_CBC_SHA256,
       TLS_RSA_WITH_AES_256_CBC_SHA256"
    />

However, currently this format is not supported by TomcatJSS, causing the following error:

Error: SSL cipher "                TLS_DHE_RSA_WITH_AES_256_CBC_SHA" not recognized by tomcatjss
Error: SSL cipher "                TLS_DHE_RSA_WITH_AES_128_CBC_SHA256" not recognized by tomcatjss
Error: SSL cipher "                TLS_DHE_RSA_WITH_AES_256_CBC_SHA256" not recognized by tomcatjss
Error: SSL cipher "                TLS_DHE_RSA_WITH_AES_128_GCM_SHA256" not recognized by tomcatjss
Error: SSL cipher "                TLS_RSA_WITH_AES_128_CBC_SHA256" not recognized by tomcatjss
Error: SSL cipher "                TLS_RSA_WITH_AES_256_CBC_SHA256" not recognized by tomcatjss

The cipher list parser needs to be modified to support spaces and line breaks.
Comment 2 Endi Sukma Dewata 2017-05-31 23:23:38 UTC 
Fixed in master:

* https://github.com/dogtagpki/tomcatjss/commit/c14c8ec6b077721eddeddb125b9a4b0141e5e4aa
Comment 4 Geetika Kapoor 2017-06-20 10:18:06 UTC 
Test build:
===========
rpm -qa tomcatjss
tomcatjss-7.2.1-6.el7.noarch

Actual:
=========
Server.xml



           sslRangeCiphers="-TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA,-TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA,-TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA,-TLS_ECDH_RSA_WITH_AES_128_CBC_SHA,-TLS_ECDH_RSA_WITH_AES_256_CBC_SHA,-TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA,-TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,-TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,-TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,-TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,-TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,-TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,-TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,-TLS_DHE_DSS_WITH_AES_128_CBC_SHA,-TLS_DHE_DSS_WITH_AES_256_CBC_SHA,-TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA,-TLS_DHE_RSA_WITH_AES_128_CBC_SHA,-TLS_DHE_RSA_WITH_AES_256_CBC_SHA,-TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,-TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,-TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,-TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,-TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,-TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,-TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,-TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,-TLS_RSA_WITH_AES_128_CBC_SHA256,-TLS_RSA_WITH_AES_256_CBC_SHA256,-TLS_RSA_WITH_AES_128_GCM_SHA256,+TLS_RSA_WITH_3DES_EDE_CBC_SHA,+TLS_RSA_WITH_AES_128_CBC_SHA,+TLS_RSA_WITH_AES_256_CBC_SHA"


Expected:

Doesn't match the expected.

<Connector
   sslRangeCiphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
       TLS_DHE_RSA_WITH_AES_256_CBC_SHA,
       TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,
       TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,
       TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
       TLS_RSA_WITH_AES_128_CBC_SHA256,
       TLS_RSA_WITH_AES_256_CBC_SHA256"
    />
Comment 5 Endi Sukma Dewata 2017-06-20 15:03:38 UTC 
The TomcatJSS changes in comment #2 basically allow the cipher list in server.xml to be specified in multiple lines. It doesn't actually change the server.xml since the file is owned by PKI (although that can be done too in a separate ticket).

To verify this ticket, install PKI CA, modify the cipher list from one long line into multiple lines as shown in the original bug description, restart the CA, and make sure that it is working fine.
Comment 6 Geetika Kapoor 2017-06-21 09:48:32 UTC 
Test build:
===========
rpm -qa tomcatjss
tomcatjss-7.2.1-6.el7.noarch

Server.xml changed after setp 1 :

cat b | tr "," "\n" | sed "s/$/,/g"

sslRangeCiphers="-TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA,
-TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA,
-TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA,
-TLS_ECDH_RSA_WITH_AES_128_CBC_SHA,
-TLS_ECDH_RSA_WITH_AES_256_CBC_SHA,
-TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA,
-TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,
-TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,
-TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
-TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,
-TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,
-TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
-TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
-TLS_DHE_DSS_WITH_AES_128_CBC_SHA,
-TLS_DHE_DSS_WITH_AES_256_CBC_SHA,
-TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA,
+TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
+TLS_DHE_RSA_WITH_AES_256_CBC_SHA,
+TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,
+TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,
+TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
-TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,
-TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,
-TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,
-TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+TLS_RSA_WITH_AES_128_CBC_SHA256,
+TLS_RSA_WITH_AES_256_CBC_SHA256,
-TLS_RSA_WITH_AES_128_GCM_SHA256,
-TLS_RSA_WITH_3DES_EDE_CBC_SHA,
-TLS_RSA_WITH_AES_128_CBC_SHA,
-TLS_RSA_WITH_AES_256_CBC_SHA"

With above mentioned format CA starts well.
Comment 7 errata-xmlrpc 2017-08-01 21:09:17 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-2017:2079
Note You need to log in before you can comment on or make changes to this bug.