-
Notifications
You must be signed in to change notification settings - Fork 453
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
Check for suspicious gradle-wrapper.jar #1440
Conversation
src/settings.ts
Outdated
@@ -17,6 +17,9 @@ const changeItem = { | |||
never: 'Never' | |||
}; | |||
|
|||
const allow = 'Allow'; | |||
const disallow = 'Disallow'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'Do not trust'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
677d930
to
95e162a
Compare
Signed-off-by: Snjezana Peco <[email protected]>
@fbricon I have update the PR. |
Before a Gradle wrapper is executed, its checksum is verified against the list of wrappers publicly released by the Gradle team. If the checksum doesn't match a known good checksum, a security warning is displayed (actually an error, so it stays visible): The link opens the corresponding wiki page. If you trust the wrapper to be executed, the application settings.jon will be updated like: "java.imports.gradle.wrapper.checksums": [
{
"sha256": "504b38a11c466aecb2f5c0b0d8ce0ed7ffa810bf70b9b7a599c570051be8fb4e",
"allowed": true
}
], and the wrapper will be used. If you don't trust it, The default Gradle version embedded in Buildship will be used to build your project until the wrapper is explicitly trusted. |
Requires eclipse-jdtls/eclipse.jdt.ls#1434
Signed-off-by: Snjezana Peco [email protected]