You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.
AFAICT, they only use that token to create a short-lived/less-privileged registration token.
Could the registration tokens be created from the webhook instead and passed in to the VMs on launch? and that IAM policy be put only on the webhook, not the VM? Then if hostile code sneaks into the build, it can't get persistent admin access (this way, at least).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First, thanks for writing this!
I'm doing a quick audit. I see that:
workflow
andadmin:org
scopes".Could the registration tokens be created from the webhook instead and passed in to the VMs on launch? and that IAM policy be put only on the webhook, not the VM? Then if hostile code sneaks into the build, it can't get persistent admin access (this way, at least).
The text was updated successfully, but these errors were encountered: