summaryrefslogtreecommitdiff
path: root/fsverity_init
diff options
context:
space:
mode:
authorVictor Hsieh <victorhsieh@google.com>2022-10-05 17:15:54 -0700
committerVictor Hsieh <victorhsieh@google.com>2022-12-05 11:04:08 -0800
commit1b8ac1a87982424482d9ef0c464f1a0af6598ca3 (patch)
tree2800c4cddd34a98775432cc588d1f9acb7650b40 /fsverity_init
parent2377248cd64666563178acb92b5580776bc4acf2 (diff)
downloadsecurity-1b8ac1a87982424482d9ef0c464f1a0af6598ca3.tar.gz
Do not require fs-verity built-in signature
There are use cases where fs-verity without signature is helpful. Relax the restriction. Existing use cases (other than work-in-progress features) of fs-verity in AOSP has been migrated to signature check in userspace. Bug: 249158715 Test: CtsAppSecurityHostTestCases:android.appsecurity.cts.ApkVerityInstallTest Ignore-AOSP-First: Security implication requires some change in frameworks/base Change-Id: I6b7d7143485ad304d4aa7e8a924d32d558540b92 Merged-In: I6b7d7143485ad304d4aa7e8a924d32d558540b92
Diffstat (limited to 'fsverity_init')
-rw-r--r--fsverity_init/main.cpp6
1 files changed, 0 insertions, 6 deletions
diff --git a/fsverity_init/main.cpp b/fsverity_init/main.cpp
index 3f75dca9..b502b91c 100644
--- a/fsverity_init/main.cpp
+++ b/fsverity_init/main.cpp
@@ -48,12 +48,6 @@ int main(int argc, const char** argv) {
return -1;
}
} else if (command == "--lock") {
- // Requires files backed by fs-verity to be verified with a key in .fs-verity
- // keyring.
- if (!android::base::WriteStringToFile("1", "/proc/sys/fs/verity/require_signatures")) {
- PLOG(ERROR) << "Failed to enforce fs-verity signature";
- }
-
if (!android::base::GetBoolProperty("ro.debuggable", false)) {
if (keyctl_restrict_keyring(keyring_id, nullptr, nullptr) < 0) {
PLOG(ERROR) << "Cannot restrict .fs-verity keyring";