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

Potential malware on the zip file #48

Closed
rafamvc opened this issue Mar 9, 2013 · 7 comments
Closed

Potential malware on the zip file #48

rafamvc opened this issue Mar 9, 2013 · 7 comments

Comments

@rafamvc
Copy link

rafamvc commented Mar 9, 2013

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/

@L2G
Copy link

L2G commented Mar 11, 2013

Where did your download come from?

This may be related to #47, but it's hard for me to say as a bystander. Nope. Files are straight outta the GitHub repo.

@rafamvc
Copy link
Author

rafamvc commented Mar 11, 2013

@L2G
Copy link

L2G commented Mar 11, 2013

Hmmm. Looks like a fair cop to me. SHA256 digest is identical.

Do be mindful of the possibility of false positives, though.

@adoxa??

@rafamvc
Copy link
Author

rafamvc commented Mar 11, 2013

You can rescan your own copy too.

On Mon, Mar 11, 2013 at 3:06 PM, Larry Gilbert notifications@github.comwrote:

Hmmm. Looks like a fair cop to me. SHA256 digest is identical.

@adoxa https://github.com/adoxa??


Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-14745956
.

@L2G
Copy link

L2G commented Mar 11, 2013

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.

@L2G
Copy link

L2G commented Mar 11, 2013

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?

@adoxa
Copy link
Owner

adoxa commented Mar 12, 2013

The warnings are caused by ANSI-LLW.exe. 1.60 was an attempt to remove dependence on it, but it failed; 1.61 has gone back to using it, but compiled differently, so the warnings are reduced.

@adoxa adoxa closed this as completed Mar 12, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants