Commit 336c2fb2 authored by Pavol Marko's avatar Pavol Marko Committed by Commit Bot

Remove stale TODO

Remove a stale TODO. The Chrome OS sign-in Profile is now always using
the built-in certificate verifier, so there's no explitily enabled it
for certain policy values.

Bug: 972044
Test: none
Change-Id: Id4d7a2233557d4adb131199bdeb548ad43a02f42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1808862Reviewed-by: default avatarMatt Mueller <mattm@chromium.org>
Commit-Queue: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#697349}
parent ecae95ee
...@@ -147,9 +147,6 @@ bool ShouldUseBuiltinCertVerifier(Profile* profile) { ...@@ -147,9 +147,6 @@ bool ShouldUseBuiltinCertVerifier(Profile* profile) {
if (builtin_cert_verifier_enabled_pref->IsManaged()) if (builtin_cert_verifier_enabled_pref->IsManaged())
return builtin_cert_verifier_enabled_pref->GetValue()->GetBool(); return builtin_cert_verifier_enabled_pref->GetValue()->GetBool();
// TODO(https://crbug.com/939344): Also evaluate whether there are
// extension-specific certificates to be used, and if yes, enable the built-in
// cert verifier.
return base::FeatureList::IsEnabled( return base::FeatureList::IsEnabled(
net::features::kCertVerifierBuiltinFeature); net::features::kCertVerifierBuiltinFeature);
} }
......
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