Add a SECURITY.md pointing to the Chromium process

Otherwise, on GitHub, we're picking up a default github.com/google one
that points to https://g.co/vulnz

Change-Id: I5b815730649fd1d5ea40f912327bc9110916fa06
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87867
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
This commit is contained in:
David Benjamin
2026-01-26 13:43:25 -05:00
committed by Boringssl LUCI CQ
parent cb3b2fda3d
commit 1474012d8b
+1
View File
@@ -0,0 +1 @@
To file a security issue, use the [Chromium process](https://www.chromium.org/Home/chromium-security/reporting-security-bugs/) and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.