Closed twaldrop closed 6 years ago
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build finished.
retest
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
From what I found, ssl protocols have to be disabled in /etc/haproxy/haproxy.cfg
which is terminating the SSL connection. SSLv3 is already disabled there. To also disable TLSv1.0 and TLSv1.1 you just need to change all the bind
lines in haproxy.cfg
as follows:
- bind :::5000 ssl crt /etc/haproxy/openstack.pem no-sslv3 ciphers AES128-SHA:AES256-SHA
+ bind :::5000 ssl crt /etc/haproxy/openstack.pem no-sslv3 no-tlsv10 no-tlsv11 ciphers AES128-SHA:AES256-SHA
I verified that doing this did in fact disable TLSv1.0 and TLSv1.1. You can check if TLS v1.0, v1.1 and v1.2 are enabled or not by running the following commands, respectively:
openssl s_client -connect HOSTNAME:443 -tls1
openssl s_client -connect HOSTNAME:443 -tls1_1
openssl s_client -connect HOSTNAME:443 -tls1_2
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
retest
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.