Commit b68b0360 authored by Chris Thompson's avatar Chris Thompson Committed by Chromium LUCI CQ

Add removal notice to SSLVersionMin policy

Support for the enterprise bypass of the TLS 1.0/1.1 removal will be
removed in May 2021. This adds a notice to the policy page to clarify
this. The sunsetting of this bypass has been previously announced
in https://www.chromestatus.com/feature/5759116003770368,
https://security.googleblog.com/2018/10/modernizing-transport-security.html
(in 2018), and https://blog.chromium.org/2019/10/chrome-ui-for-deprecating-legacy-tls.html
(in 2019).

Bug: 896013
Change-Id: Ib0cb2ba9bc8a925a1a8bfd3ee17995ae0a23bd3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569811
Commit-Queue: Chris Thompson <cthomp@chromium.org>
Reviewed-by: default avatarDavid Benjamin <davidben@chromium.org>
Reviewed-by: default avatarJulian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833812}
parent 38837100
...@@ -13941,7 +13941,9 @@ ...@@ -13941,7 +13941,9 @@
'id': 279, 'id': 279,
'caption': '''Minimum SSL version enabled''', 'caption': '''Minimum SSL version enabled''',
'tags': [], 'tags': [],
'desc': '''Setting the policy to a valid value means <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> won't use SSL/TLS versions less than the specified version. Unrecognized values are ignored. 'desc': '''Warning: Support for suppressing the TLS 1.0/1.1 warning will be removed from <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> starting in version 91 (around May 2021) and this policy will stop working then.
Setting the policy to a valid value means <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> won't use SSL/TLS versions less than the specified version. Unrecognized values are ignored.
If this policy is not set, then <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> will show an error for TLS 1.0 and TLS 1.1, but the user will be able to bypass it.''', If this policy is not set, then <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> will show an error for TLS 1.0 and TLS 1.1, but the user will be able to bypass it.''',
}, },
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment