boringssl/SECURITY.md at 1474012d8b89d4c9060947c4e63a86db6944f4c5

mirror of https://boringssl.googlesource.com/boringssl synced 2026-07-21 14:43:51 +00:00

Files

T

David Benjamin 1474012d8b 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>

2026-01-26 11:02:17 -08:00

254 B

Raw Blame History

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

254 B Raw Blame History

254 B

Raw Blame History