Shepherd help for dependency vulnerabilities.
Add a link to a document with some hints about how to use Google-internal systems to investigate these dependency bugs. Change-Id: If3b8298a42de958cd61dd602b1dc0f4c0ae18c6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4886948 Commit-Queue: Alex Gough <ajgo@chromium.org> Auto-Submit: Adrian Taylor <adetaylor@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1239235}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
8b70b16022
commit
62fd349032
@ -474,6 +474,12 @@ If you find a vulnerability in a Permission API and need to use the Global
|
||||
Permissions Kill Switch, then follow [the
|
||||
instructions](https://docs.google.com/document/d/17JeYt3c1GgghYoxy4NKJnlxrteAX8F4x-MAzTeXqP4U)
|
||||
|
||||
### Vulnerabilities in Chromium's dependencies
|
||||
|
||||
If you are handling a bug in one of Chromium's dependencies, see
|
||||
[go/howto-investigate-autovm-chromium-bugs](https://goto.google.com/howto-investigate-autovm-chromium-bugs)
|
||||
(Google-only, sorry) for some hints.
|
||||
|
||||
### Wrapping Up The Fixed Issue
|
||||
|
||||
1. Check with the developer that the issue can be closed as Fixed to allow
|
||||
|
Reference in New Issue
Block a user