virus scanner complains about winflexbison

[lexxmark]

Sorry for delay,

I faced the same problem when migrated to Visual Studio 2017. May be it's connected.
I've just marked win_flex.exe as false positive.
If you know how to fix it, let me know.

Regards,
Alex

[sg495]

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.

[lexxmark]

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.

[lexxmark]

I have updated win_flex_bison (reverted to VS 2015).
Please check new files and report an issue if virus scanners still detects something.