Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-30478

[8.1.0.GA] - Missing documentation regarding cipher-suite-names

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Documentation, Security
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Improve documentation for the cipher-suite-filter and cipher-suite-names attributes on server-ssl-context:

      https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/8.0/html-single/configuring_ssltls_in_jboss_eap/index#server-ssl-context-attributes_default

      Here is the current extracts:

      cipher-suite-filter, it has the following description:

      The filter to apply to specify the enabled cipher suites. This filter takes a list of items delimited by colons, commas, or spaces.

      The documentation for cipher-suite-names - the filter to apply to specify the enabled cipher suites for TLSv1.3, on the other hand, does not specify what delimiters to use on this list, even though it does not accept commas, different from what was described on the other parameter.

      To clarify the following Javadoc can be referenced for how these Strings are parsed internally:

      cipher-suite-filter

      https://wildfly-security.github.io/wildfly-elytron/documentation/api/upstream/org/wildfly/security/ssl/CipherSuiteSelector.html#fromString(java.lang.String)

      cipher-suite-names

      https://wildfly-security.github.io/wildfly-elytron/documentation/api/upstream/org/wildfly/security/ssl/CipherSuiteSelector.html#fromNamesString(java.lang.String)

      Although the former does support commas for backwards compatibility this is not the preferred delimiter and both should use colons.

              dfenness@redhat.com Darren Fennessy
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: