-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use SHA-1 hashes instead of mutable refs for GH action dependencies #3402
Comments
Looks like it is supported by dependabot: dependabot/dependabot-core#2835 |
@dduportal thanks for the link, it's where I found out about https://github.com/sethvargo/ratchet, which in combination with https://github.com/lindell/multi-gitter allowed me to quickly pin all GitHub actions. @daniel-beck thanks for the suggestion, let me know if you want me to do the same on some @jenkinsci repositories, it shouldn't take me long to do it now that I have a working script 😉 |
FWIW my preference is to keep |
Yes sorry about that, read too fast your issue first, I reviewed my script and my pull requests to keep We (infra team) agree with you, I'll rework/review the pull requests to also keep the |
For the record, there are currently 43 distinct GitHub actions used in @jenkins-infra repositories, List of unique GHA used:
And before these pull requests, 71 actions with different versions, Actions with all their versions:
|
…actions with their SHA-1 instead of their version number
…actions with their SHA-1 instead of their version number
Almost all pull requests taken in account, closing this issue. For the record here is the script I've used: #3408 |
…their SHA-1 instead of their version number (#3408)
Service(s)
GitHub
Summary
Looking at #3355 and some of the repos linked there, none of the actions use a SHA-1 reference to tags.
As a security best practice, SHA-1 references instead of tags (or branches) should be used, to prevent upstream from replacing the tag introducing behavior changes, in the worst case malicious behavior. I think it's safe to continue using these tags for
action/…
actions or our own, but third party actions should be handled more strictly.See also jenkinsci/jenkins#7113 which brought this problem up in the context of actions used in
jenkinsci/jenkins
.Reproduction steps
No response
The text was updated successfully, but these errors were encountered: