[CT] Re-enable Static CT API policy enforcement

The enforcement logic now ignores logs with unset log types among other
changes.

Bug: 370724580
Change-Id: Icb7eb887a5891e351bb3dbf84cb17050bb0f277d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5957874
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Joe DeBlasio <jdeblasio@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1372943}

This commit is contained in:

Mustafa Emre Acer

2024-10-23 21:38:38 +00:00

committed by

Chromium LUCI CQ

parent 1c296fc23b

commit 25cb1f94e7

1 changed files with 1 additions and 1 deletions

									
										2

net/base/features.cc
									
				@ -606,7 +606,7 @@ BASE_FEATURE(kEncryptedAndPlaintextValuesAreInvalid,

				BASE_FEATURE(kEnableStaticCTAPIEnforcement,

				             "EnableStaticCTAPIEnforcement",

				             base::FEATURE_DISABLED_BY_DEFAULT);

				             base::FEATURE_ENABLED_BY_DEFAULT);

				BASE_FEATURE(kDiskCacheBackendExperiment,

				             "DiskCacheBackendExperiment",

[CT] Re-enable Static CT API policy enforcement

2 net/base/features.cc

2

net/base/features.cc