Windows defender finds a virus in current master branch

[rmn20]

I'm using Windows 10 LTSC
At the moment, on the state of this commit, windows defender finds a virus in the master branch.

[anzz1]

Breaking News
AV ""product"" sucks ass, water is wet.

To be clear, I'm not calling you stupid, I'm calling your AV software stupid. Users are not to blame, the companies should make passable products instead of falsely advertising them as such.

I've wasted so much time sending legitimate software to various AV companies to be whitelisted that I can't even count; all the while the AV companies do nothing to stop the spread of actually malicious stuff.

I'm done doing that though. If someone else wants to send the binaries to AV companies to be whitelisted so they don't hit the "unknown file, must be a virus" mark, feel free to do that.

I cannot fully express my opinion towards AV companies within the GitHub etiquette but I'm sure you can read between the lines.

[h-h-h-h]

On virustotal.com, MaxSecure thinks llama-master-34c1072-bin-win-avx2-x64.zip from the release page is "Trojan.Malware.300983.susgen".

When I compile the codebase as "x64-Release" with Visual Studio 2022, I get the same 6 .exe files as in the ready-made release (by their names). Of those, only test-quantize.exe is flagged on virustotal.com, again as "Trojan.Malware.300983.susgen".

In my understanding, test-quantize.exe is made out of tests/test-quantize.c. I could only find the method calls ggml_quantize_q4_0() and ggml_quantize_q4_1() there that call into the rest of the codebase. And those methods are also called in other code that I assume is used to create the other .exe files which aren't flagged.

So, flagging test-quantize.exe in my build seems irrational. But the app also worked without it for me; so you can just delete it.

What .exe files are flagged exactly how is different for the initially mentioned official download, though.

[anzz1]

So, flagging test-quantize.exe in my build seems irrational.

You are now confusing antivirus software with something that is rational.

I can't fathom how they are so bad at detecting viruses while simultaneously flagging everything that isn't, even having all the resources in the world and being made by billion dollar companies. There is simply no excuse. There would be some very simple ways of improving their heuristics by a leap, lot of it involving following the codepaths to what actual system libraries are accessed and what are the actual syscalls being made. However, they dont do that and basically resort to the same CTRL+F style ""heuristics"" that has been the modus operandi since the 1990s. It simply doesn't and can't work properly and is a completely irrational approach. Maybe it did once make a little bit of sense, when there were like 10 different viruses total in existence and everything was shared in diskettes and floppies. It however, does not make any sense today.

If your security plan is a blindfolded monkey with a shotgun, you can hardly blame the result to be illogical.