Disabling the SSLv3 protocol
You can disable SSLv3 after you upgrade to a system that no longer requires this protocol.
About this task
Newer levels of the IBM Java virtual machine (JVM) now disable SSLv3 by default, because it is no
longer considered a secure protocol. This protocol can be affected by the Padding Oracle On
Downgraded Legacy Encryption (POODLE) vulnerability. Systems with the POODLE fix should not use
SSLv3 connections. However, older systems that do not have this fix still connect by using SSLv3.
Copy Services Manager enables limited support for the SSLv3
protocol to accommodate these older systems. After you upgrade your system, you need to disable
SSLv3.
Note: This procedure is not necessary for Copy Services Manager on the HMC because it only uses TLSv1.2
connections.
Disabling the SSLv3 protocol for DS8000 connections
You can disable the SSLv3 protocol for DS8000 connections.
About this task
Perform the following steps to disable SSLv3 in Copy Services Manager for DS8000 connections. You can either edit the essclient.properties and jvm.options files directly, or use the chsystem command.
Note: This procedure is not necessary for Copy Services Manager on the HMC because it only uses TLSv1.2
connections.
Disable SSLv3 on DS8000 by editing the essclient.properties and jvm.options files
You can edit the essclient.properties and jvm.options files to change the protocol from SSLv3 to TLSv1.2 for DS8000 connections.
About this task
Procedure
Disable SSLv3 on DS8000 by using the chsystem command
You can use the chsystem command to change the protocol from SSLv3 to TLSv1.2 for DS8000 connections.
About this task
Procedure
Disabling the SSLv3 protocol for z/OS host connections
You can disable the SSLv3 protocol for z/OS host connections by using the chsystem command.