Jump to: navigation, search

Difference between revisions of "Jetty/Howto/CipherSuites"

< Jetty‎ | Howto
(New page: {{Jetty Howto | introduction = The SSL cipher suites used by Jetty are provided by the Java Virtual Machine. Please refer to this [http://java.sun.com/javase/6/docs/technotes/guides/secur...)
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Jetty Howto
 
{{Jetty Howto
 
| introduction =  
 
| introduction =  
The SSL cipher suites used by Jetty are provided by the Java Virtual Machine. Please refer to this [http://java.sun.com/javase/6/docs/technotes/guides/security/SunProviders.html#SunJSSEProvider documentation] for more information on the available cipher suites.
+
 
 +
{{Jetty Redirect|http://www.eclipse.org/jetty/documentation/current/configuring-ssl.html}}
 +
 
 +
The Java Virtual Machine provides the SSL cipher suites that Jetty uses. See [http://java.sun.com/javase/6/docs/technotes/guides/security/SunProviders.html#SunJSSEProvider JSSE Provider documentation] for more information on the available cipher suites.
  
 
| steps =
 
| steps =
===Enable Cipher Suites===
+
===Enabling Cipher Suites===
In the event any required cipher suite is not enabled by default, Jetty provides a mechanism that allows enabling the cipher suite for the specific SSL connector during Jetty startup. The following changes will need to be made to jetty.xml configuration file. Please note that the cipher suites need to be specified in the required preference order.  
+
If a cipher suite that you require is not enabled by default, Jetty provides a mechanism that lets you enable the cipher suite for a specific SSL connector during Jetty startup. Be aware that you must specify cipher suites in preference order.  
 +
 
 +
Here's an example of how to configure the SslSocketConnector with included cipher suites:
  
 
<source lang="xml">
 
<source lang="xml">
Line 29: Line 34:
 
</source>
 
</source>
  
===Disable Chipher Suites===
+
Note that for the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/server/ssl/SslSelectChannelConnector.html SslSelectChannelConnector], the correct way to configure ssl is using an [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/http/ssl/SslContextFactory.html SslContextFactory] as discussed on the [[Jetty/Howto/Configure_SSL | SSL Configuration]] page. There is an example in the jetty distribution in '''/etc/jetty-ssl.xml'''.
If a vulnerability is discovered in a cipher, or if it is considered too weak to use, it is possible to exclude it during Jetty startup. The following changes will need to be made to jetty.xml configuration file. In the event the cipher suites are both included and excluded as part of the same configuration, the exclude operation is performed after the include operation.
+
 
 +
 
 +
 
 +
===Disabling Chipher Suites===
 +
If a vulnerability is discovered in a cipher, or if it is considered too weak to use, you can exclude it during Jetty startup. You need to make the following changes to the <tt>jetty.xml</tt> configuration file. Jetty performs the exclude operation after the include operation. Therefore, If a cipher suite is both included and excluded as part of the same configuration, it is disabled.
  
 
<source lang="xml">
 
<source lang="xml">

Latest revision as of 15:34, 23 April 2013



Introduction


The Java Virtual Machine provides the SSL cipher suites that Jetty uses. See JSSE Provider documentation for more information on the available cipher suites.


Steps

Enabling Cipher Suites

If a cipher suite that you require is not enabled by default, Jetty provides a mechanism that lets you enable the cipher suite for a specific SSL connector during Jetty startup. Be aware that you must specify cipher suites in preference order.

Here's an example of how to configure the SslSocketConnector with included cipher suites:

<Call name="addConnector">
  <Arg>
    <New class="org.mortbay.jetty.security.SslSocketConnector">
      <Set name="Port">8443</Set>
      <Set name="maxIdleTime">30000</Set>
      ...
      <Set name="IncludeCipherSuites">
        <Array type="java.lang.String">
          <Item>TLS_DHE_DSS_WITH_AES_128_CBC_SHA</Item>
          <Item>TLS_DHE_RSA_WITH_AES_128_CBC_SHA</Item>
          <Item>TLS_RSA_WITH_AES_128_CBC_SHA</Item>
          <Item>TLS_DHE_DSS_WITH_AES_256_CBC_SHA</Item>
          <Item>TLS_DHE_RSA_WITH_AES_256_CBC_SHA</Item>
          <Item>TLS_RSA_WITH_AES_256_CBC_SHA</Item>
        </Array>
      </Set>
    </New>
  </Arg>
</Call>

Note that for the SslSelectChannelConnector, the correct way to configure ssl is using an SslContextFactory as discussed on the SSL Configuration page. There is an example in the jetty distribution in /etc/jetty-ssl.xml.


Disabling Chipher Suites

If a vulnerability is discovered in a cipher, or if it is considered too weak to use, you can exclude it during Jetty startup. You need to make the following changes to the jetty.xml configuration file. Jetty performs the exclude operation after the include operation. Therefore, If a cipher suite is both included and excluded as part of the same configuration, it is disabled.

<Call name="addConnector">
  <Arg>
    <New class="org.mortbay.jetty.security.SslSocketConnector">
      <Set name="Port">8443</Set>
      <Set name="maxIdleTime">30000</Set>
      ...
      <Set name="ExcludeCipherSuites">
        <Array type="java.lang.String">
          <Item>SSL_RSA_WITH_3DES_EDE_CBC_SHA</Item>
          <Item>SSL_DHE_RSA_WITH_DES_CBC_SHA</Item>
          <Item>SSL_DHE_DSS_WITH_DES_CBC_SHA</Item>
        </Array>
      </Set>
    </New>
  </Arg>
</Call>