-
Notifications
You must be signed in to change notification settings - Fork 128
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
Potential malware on the zip file #48
Comments
Where did your download come from?
|
Hmmm. Looks like a fair cop to me. SHA256 digest is identical. Do be mindful of the possibility of false positives, though. @adoxa?? |
You can rescan your own copy too. On Mon, Mar 11, 2013 at 3:06 PM, Larry Gilbert notifications@github.comwrote:
|
Well, I could (and actually, I already did), but all that tells me is the same result that VirusTotal gives for the specific virus scanner I have. :-) (That's McAfee in my case.) I too have the feeling that the number of hits alone in that report is cause for concern. Removing those zip and tarball downloads would be done by removing those Git tags, but the files that trigger those virus warnings and that may be infected would still be sitting there in the Git repo. I guess it's up to @adoxa as to how deeply he wants to scrub the repo for old, infected binaries. |
By the way, is there a reason you have to use 1.53 instead of the latest (1.61)? Or were you concerned about the virus warnings in general? |
The warnings are caused by |
While doing a install on a computer with antivirus, it showed that this file contains malware.
Here is a online scan of the file:
https://www.virustotal.com/en/file/62e9f6fa2d808dc400c8a1b77a96e7d20b5640e8ca3c4b8ea8dc0566485e17bc/analysis/1362801198/
The text was updated successfully, but these errors were encountered: