Recommendation from Chrome security folks was to use the Chromium
process for security bugs. Also crbug.com/boringssl links work now.

Also since I guess the "bug tracker" is now an "issue tracker", I
suppose we can say "issue". Meh.

Change-Id: I6c4bb81165989b3ec5f98041e4c6c2cdf52fca2f
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70588


Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>