Only disable SHA-1 for local trust anchors if there's a PrefService
SHA-1 is being phased out, and beginning with M57, SHA-1 certificates signed by locally installed trust anchors is being disabled by default. To re-enable, Enterprises should set an EnableSha1ForLocalAnchors policy to allow it. However, for platforms without enterprise policies, or for embedders, this raises a question about what the default state should be - enabled or disabled. As Chrome itself expects there to be non-trivial impact (thus, the policy, supported until 1 Jan 2019), it is safer to leave the current behaviour, enabling SHA-1 for these certs, on by default, and leave it to embedders to disable (via the SSLConfig/SSLConfigService). If embedders support preferences, that's seen as sufficient support to enable some degree of run-time control/flexibility, thus the default is moved from //net to //components/ssl_config. Embedders using //net will continue to support SHA-1 anchors by default, while embedders that include //components/ssl_config (and use it) will disable it by default. BUG=673036 Review-Url: https://codereview.chromium.org/2613533004 Cr-Commit-Position: refs/heads/master@{#441481}
Showing
Please register or sign in to comment