Versions Compared

Old Version 5

changes.mady.by.user Former user

Saved on

compared with

New Version 6

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The transport level security protocol of the Tomcat server is configured in the the <PRODUCT_HOME>/conf/tomcat/catalina-server.xml file. Note that the ssLprotocol attribute is set to "TLS" by default. 

See the following topics for detailed configuration options:

Table of Contents
maxLevel3
minLevel3

Disable SSL version 3 on Carbon server

Info

It is necessary to disable SSL version 3 in Carbon servers because of a bug (Poodle Attack) in the SSL version 3 protocol that could expose critical data encrypted between clients and servers. The Poodle Attack makes the system vulnerable by telling the client that the server does not support the more secure TLS (Transport Layer Security) protocol, and thereby forces it to connect via SSL 3.0. The effect of this bug can be mitigated by disabling SSL version 3 protocol for your server.

Follow the steps given below to disable SSL 3.0 support on WSO2 Carbon 4.3.0 based servers.

  1. Open the the <PRODUCT_HOME>/repository/conf/catalina-server.xml file file. 
  2. Take a backup of the the catalina-server.xml file  file and stop the Carbon server.
  3. Find the Connector configuration corresponding to TLS (usually, this connector has the port set to 9443 and the the sslProtocol as TLS).

    • If you are using JDK 1.6, remove the the sslProtocol="TLS" attribute  attribute from the configuration and replace it with with sslEnabledProtocols="TLSv1" as  as shown below.

      Code Block
      <Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
                port="9443"
                bindOnInit="false"
                sslEnabledProtocols="TLSv1"

    •  If you are using JDK 1.7, remove the the sslProtocol="TLS" attribute from the above configuration and replace it with with sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" as  as shown below.

      Code Block
      <Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
                port="9443"
                bindOnInit="false"
                sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" 

...

  2. Start the server.
     Note
    In some Carbon products, such as WSO2 ESB and WSO2 API Manager, pass-thru 
...
  1. Open 
    transports are enabled. Therefore, to disable SSL version 3 in such products, the axis2.xml file 
     from 
    stored in the <PRODUCT_HOME>/repository/conf/axis2/
     directory.
  2. Find the transportReceiver configuration element for org.apache.synapse.transport.passthru.PassThroughHttpSSLListener.
    • If you are using JDK 1.6, add the following parameter under transportReceiver.
       Code Block
      <parameter name="HttpsProtocols">TLSv1</parameter> 
    • If you are using JDK 1.7, add the following parameter under transportReceiver.
       Code Block
      <parameter name="HttpsProtocols">TLSv1,TLSv1.1,TLSv1.2</parameter> 
  3.  directory should also be configured.
To test if SSL version 3 is disabled:
  1. Download TestSSLServer.jar from here.
  2. Execute the following command to test the transport.:
     Code Block
    java -jar TestSSLServer.jar localhost 9443 
    To test the pass-thru transport, use the following command with the corresponding port:
     Code Blockjava -jar TestSSLServer.jar localhost 8243
  3. The output of the command before and after disabling SSL version 3 is shown below.

    Before SSL version 3 is disabled:
     Code Block
    Supported versions: SSLv3 TLSv1.0
Deflate compression: no
Supported cipher suites (ORDER IS NOT SIGNIFICANT):
  SSLv3
     RSA_EXPORT_WITH_RC4_40_MD5
     RSA_WITH_RC4_128_MD5
     RSA_WITH_RC4_128_SHA
     RSA_EXPORT_WITH_DES40_CBC_SHA
     RSA_WITH_DES_CBC_SHA
     RSA_WITH_3DES_EDE_CBC_SHA
     DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
     DHE_RSA_WITH_DES_CBC_SHA
     DHE_RSA_WITH_3DES_EDE_CBC_SHA
     RSA_WITH_AES_128_CBC_SHA
     DHE_RSA_WITH_AES_128_CBC_SHA
     RSA_WITH_AES_256_CBC_SHA
     DHE_RSA_WITH_AES_256_CBC_SHA
  (TLSv1.0: idem)
    After SSL version 3 is disabled:
     Code Block
    Supported versions: TLSv1.0
Deflate compression: no
Supported cipher suites (ORDER IS NOT SIGNIFICANT):
  TLSv1.0
     RSA_EXPORT_WITH_RC4_40_MD5
     RSA_WITH_RC4_128_MD5
     RSA_WITH_RC4_128_SHA
     RSA_EXPORT_WITH_DES40_CBC_SHA
     RSA_WITH_DES_CBC_SHA
     RSA_WITH_3DES_EDE_CBC_SHA
     DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
     DHE_RSA_WITH_DES_CBC_SHA
     DHE_RSA_WITH_3DES_EDE_CBC_SHA
     RSA_WITH_AES_128_CBC_SHA
     DHE_RSA_WITH_AES_128_CBC_SHA
     RSA_WITH_AES_256_CBC_SHA
     DHE_RSA_WITH_AES_256_CBC_SHA
Disable weak ciphers in Carbon server
A cipher is an algorithm for performing encryption or decryption. When the the sslprotocol is  is set to "TLS", only the TLS and default ciphers are enabled by default. However, note that the strength of the ciphers will not be considered when they are enabled. Therefore, to disable the weak ciphers, you must ensure that only the ciphers you want your server to support are entered for the ciphers attribute in a comma-separated list. Also, if you do not add this cipher attribute or keep it blank, all SSL ciphers by JSSE will be supported by your server, thereby enabling the weak ciphers.
  1. Go to the catalina-server.xml file in the <PRODUCT_HOME>/repository/conf/tomcat directory.
  2. Take a backup of  the the catalina-server.xml file  file and stop the Carbon server (same as  for for disabling SSL version 3).
  3. Add the cipher attribute to the existing configuration in the catalina-server.xml file by adding the list of ciphers that you want your server to support as follows: ciphers="<cipher-name>,<cipher-name>".
     Code Block
    ciphers="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,
         TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,
         SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
  4. Start the server.