chromium/src
0
Fork 0
Code Activity

[m135][crypto] Disable labelling Win unexportable keys

Browse Source 
Disable LabelWindowsUnexportableKeys. It looks like with the feature
enabled, keys created by the installer as administrator cannot be read
by Chrome running as a normal user.

(cherry picked from commit 71d320df58)

Bug: 400919466
Fixed: 401008108
Change-Id: Id75ae4da439203b880f3a9298b2972cdb0f5d486
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6329457
Auto-Submit: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1428391}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6334104
Cr-Commit-Position: refs/branch-heads/7049@{#131}
Cr-Branched-From: 2dab7846d0951a552bdc4f350dad497f986e6fed-refs/heads/main@{#1427262}
This commit is contained in:
Nina Satragno
2025-03-06 12:08:40 -08:00
committed by Chromium LUCI CQ
parent 1dadb9cf53
commit 86a4264004
1 changed files with 2 additions and 2 deletions

4
crypto/features.cc

@ -12,9 +12,9 @@ BASE_FEATURE(kProcessBoundStringEncryption,
"ProcessBoundStringEncryption",
base::FEATURE_DISABLED_BY_DEFAULT);
// Enabled by default on M135. Disable on or after M138.
// Disabled by default.
BASE_FEATURE(kLabelWindowsUnexportableKeys,
"LabelWindowsUnexportableKeys",
base::FEATURE_ENABLED_BY_DEFAULT);
base::FEATURE_DISABLED_BY_DEFAULT);
} // namespace crypto::features