Skip to content
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

Gradle 6.4 wrapper incorrectly marked as potentially malicious #1492

Closed
lptr opened this issue Jun 12, 2020 · 5 comments
Closed

Gradle 6.4 wrapper incorrectly marked as potentially malicious #1492

lptr opened this issue Jun 12, 2020 · 5 comments

Comments

@lptr
Copy link

lptr commented Jun 12, 2020

I'm running VSCode on my macOS Catalina, using an SSH remote to open a Java project on a Windows 10 machine. Upon opening the project (see https://github.com/gradle/native-platform/tree/b8f27b864ff82621cb80e127579c1a75b682be91) I got the following warning pop-up:

image

The repo at this time uses a wrapper JAR from Gradle 6.4. The SHA256 of the JAR is 70239e6ca1f0d5e3b2808ef6d82390cf9ad58d3a3a0d271677a51d1b89475857, which matches the officially published one (see https://services.gradle.org/versions/all and https://services.gradle.org/distributions/gradle-6.4-wrapper.jar.sha256).

This means that the JAR should not be flagged, yet it is.

Environment
  • Operating System: macOS Catalina / Windows 10
  • JDK version: OpenJDK 11
  • Visual Studio Code version: 1.45.1
  • Java extension version: 0.62.0
@snjeza
Copy link
Contributor

snjeza commented Jun 12, 2020

I can't reproduce the issue.
Is there the ~/.tooling/gradle/checksums/gradle-6.4-wrapper.jar.sha256 file on your ssh server?

@lptr
Copy link
Author

lptr commented Jun 12, 2020

Yes, and it has the correct contents:

PS C:\Users\vmadmin\.tooling\gradle\checksums> cat gradle-6.4-wrapper.jar.sha256
70239e6ca1f0d5e3b2808ef6d82390cf9ad58d3a3a0d271677a51d1b89475857

@lptr
Copy link
Author

lptr commented Jun 12, 2020

Where do these files come from? Is it possible that they were updated after I got the error?

@snjeza
Copy link
Contributor

snjeza commented Jun 12, 2020

Where do these files come from? Is it possible that they were updated after I got the error?

Yes. You probably face a connection limit. Could you reproduce the error when starting VS Code again?

@fbricon
Copy link
Collaborator

fbricon commented Jul 1, 2020

Should be fixed with eclipse-jdtls/eclipse.jdt.ls#1486

@fbricon fbricon closed this as completed Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants