问题原文
原帖链接 · André Freitas · CC BY-SA 3.0
I'm trying to pass the Trustwave pci DSS scan but i can't because it fails in "TLSv1.0 supported" and i think the problem is in GCE HTTPS loadbalancer that enables TLSv 1.0, 1.1 and 1.2 by default (https://cloud.google.com/compute/docs/load-balancing/http/#tls_support). I have tested my instances locally with openssl and with cipherscan (https://github.com/jvehent/cipherscan) and in either one i was only able to get connection using TLSv1.2 ciphers. It i try to use the same tools using the public ip of GCE HTTS Load Balancer i can connect using TLSv1,TLSv1.1,TLSv1.2.
社区高分解答
原帖链接 · pfcarrier · CC BY-SA 3.0
For anyone stumbling on this ; it is now possible to define an SSL-policy that can be applied to the target-https-proxies created by a GCE HTTPS load balancer.
The following command allow to create a policy that, to my knowledge, would had met the requirement for the mentioned Trustwave pci DSS scan in OP question.
$ gcloud beta compute ssl-policies create pci_dss_ssl_policy \
--profile MODERN --min-tls-version 1.2
List the existing target-https-proxies with :
$ gcloud beta compute target-https-proxies list
Apply the created policy to a given target-https-proxies with :
$ gcloud beta compute target-https-proxies update \
NAME_OF_HTTPS_TARGET --ssl-policy pci_dss_ssl_policy
For further reference, the ssl-policies is your friend. E.g. if one want to further restrict the policy using a custom list of cipher.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
