Skip to content

Commit 6e51bde

Browse files
committed
client: don't disable TLSv1, TLSv1.1 by default that breaks VMware env
This fixes the issue that TLSv1 and TLSv1.1 are still used by CloudStack management server to communicate with VMware vCenter server. With the current defaults, the setup/deployment on VMware fails. Users/admins can however setup the security file according to their env needs to disable TLSv1 and TLSv1.1 for server sockets (8250/agent service for example). Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
1 parent 8b25fdf commit 6e51bde

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

client/conf/java.security.ciphers.in

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,4 @@
1515
# specific language governing permissions and limitations
1616
# under the License.
1717

18-
jdk.tls.disabledAlgorithms=SSLv2Hello, SSLv3, TLSv1, TLSv1.1, DH keySize < 128, RSA keySize < 128, DES keySize < 128, SHA1 keySize < 128, MD5 keySize < 128, RC4
18+
jdk.tls.disabledAlgorithms=SSLv2Hello, SSLv3, DH keySize < 128, RSA keySize < 128, DES keySize < 128, SHA1 keySize < 128, MD5 keySize < 128, RC4

0 commit comments

Comments
 (0)