-
Notifications
You must be signed in to change notification settings - Fork 115
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
virus scanner complains #11
Comments
Sorry for delay, I faced the same problem when migrated to Visual Studio 2017. May be it's connected. Regards, |
I have scanned different versions, and I'm going to paste here a short summary. Both Windows Defender and VirusTotal think that the win_flex issue started with your "update readme" commit 3232d5c on 5/12/2017 8.21, with WD reporting Trojan:Win32/Azden.A!cl and 6/68 engines in Virus Total reporting issues (with different levels of confidence). Before that, WD sees no issues, and only 2/68 engines in VirusTotal see generic issues. WD sees no issues with the latest version of win_bison, while 2/68 engines in VirusTotal see issues starting way back; the only specific issues is raised by Baidu, reporting Win32.Trojan.WisdomEyes. |
Thank you for such a detailed report. The problem raised once I've migrated to VS 2017. I think I should revert to VS 2015 for now to get rid of virus issues. I will do it in near weeks. I will let you know when I'm done, please check and report here the virus scan results. |
I have updated win_flex_bison (reverted to VS 2015). |
I have an issue meaning I can't install flex on our build server because the virus scanner freaks out.
I ran the check on but the prebuild binaries and my own compiled version using this virus scanner
https://www.virustotal.com/#/home/upload
The text was updated successfully, but these errors were encountered: