sepolicy: updating error message for fuzzer bindings
BUG: 249122938
Test: m
Change-Id: I562cc9207f821025180c647d4a07e433abb2cc6c
diff --git a/tools/fuzzer_bindings_check.py b/tools/fuzzer_bindings_check.py
index 1791f30..55859ac 100644
--- a/tools/fuzzer_bindings_check.py
+++ b/tools/fuzzer_bindings_check.py
@@ -51,7 +51,8 @@
sys.exit("\nerror: Service '{0}' is being added, but we have no fuzzer on file for it. "
"Fuzzers are listed at $ANDROID_BUILD_TOP/system/sepolicy/build/soong/service_fuzzer_bindings.go \n\n"
"NOTE: automatic service fuzzers are currently not supported in Java (b/232439254) "
- "and Rust (b/164122727). In this case, please ignore this for now. \n\n"
+ "and Rust (b/164122727). In this case, please ignore this for now and add an entry for your"
+ "new service in service_fuzzer_bindings.go \n\n"
"If you are writing a new service, it may be subject to attack from other "
"potentially malicious processes. A fuzzer can be written automatically "
"by adding these things: \n"
@@ -65,6 +66,8 @@
"automatically filed on you. You will find out about issues without needing "
"to backport changes years later, and the system will automatically find ways "
"to reproduce difficult to solve issues for you. \n\n"
+ "This error can be bypassed by adding entry "
+ "for new service in $ANDROID_BUILD_TOP/system/sepolicy/build/soong/service_fuzzer_bindings.go \n\n"
"- Android Fuzzing and Security teams".format(service_name))
return