Uh oh!
There was an error while loading. Please reload this page.
Safe Taskcluster scope proof - #6559
Open
LucasM0ntes wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security validation PR for a HackerOne report.
This PR is not intended to be merged.
The Taskcluster job intentionally does not read any secret value. It only calls:
/api/auth/v1/scopes/current
through taskcluster-proxy and checks whether the external PR task identity receives:
secrets:get:project/bugbug/integration
If that scope appears in the job log, the impact is proven without retrieving secret material. The secret-read endpoint itself is intentionally not
called.