-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Replace check gradle checksums with fetched script #488
Conversation
Thanks! I think that centralizing the trust model for gradle wrappers is a great idea, and I'd like for Spotless to help and be one of your pilot projects. As committed, we're trusting that the I'm also curious what @JLLeitschuh thinks. My memory is murky, but I believe he tried to get GitHub to do something like this in their vulnerability scanner, and he has since joined gradle directly, so he might know of officially supported plans. |
Do you mean a specific sha? Or a different kind of hash? |
Yep, specific sha. |
Yep can do, would just be something like this |
Although I'm curious what @JLLeitschuh has to say, I also don't see any downside to merging this now, so in it goes. Feel free to list us as a user / example config / whatever you'd like. Because this script is running on a CI server, it would be a great place for a hacker to exfiltrate all our publishing secrets, which is the nightmare scenario. Imo, especially because it is run by an individual rather than a first-party like Gradle, it would be unwise to rely on anything besides the hash, so if it were me I would make that the default usecase in your readme, but that's your call. Thanks! |
I'm wondering whether or not we (Gradle) should be hosting this instead. I agree that tying yourself to a specific SHA is better. |
I totally agree Gradle should host this. I think it could be hosted the
same way on gradle's repo if you'd be open to a PR. Good points on a
specific sha, I'll think it over.
…On Wed, Nov 13, 2019 at 1:36 PM Jonathan Leitschuh ***@***.***> wrote:
I'm wondering whether or not we (Gradle) should be hosting this instead.
I agree that tying yourself to a specific SHA is better.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#488?email_source=notifications&email_token=AAKMJPV7IOOUWNPQUPYJTBDQTRCMNA5CNFSM4JMIR472YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED7F6IQ#issuecomment-553541410>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKMJPSXBMCFKCPMXTACQE3QTRCMNANCNFSM4JMIR47Q>
.
|
I extracted this script out to a library with an easy install, proposing adding this here since it's more up to date. Idea is to make this more portable and usable in other repos