Hello, I'm having difficulties with my administered Windows 10 laptop's virus scanner (F-secure Client Security Premium) and the latest nim release 1.4. My previous nim version was 1.2.6.
So all was good with Nim 1.2.6, but after updating I began to get weird heuristics false alarms (HEUR/APC) from the scanner when compiling without the release flag: "nim c hello.nim". These false alarms won't pop up when I use the "nim c -d:release hello.nim" which I find odd.
I know this isn't your problem, I was just wondering if there's someone who has some experience and under the hood understanding what MIGHT trigger some heuristics when compiling without the release flag? I don't actually even know if it's even possible to speculate without seeing the scanner's code.
One problem at the moment is that I cannot even send a sample file to the virus scanner company because the scanner is so aggressively deleting the compiled example file... (of course I could do this with some other pc, but I don't have any windows pc at my possession only linux)
Is my only solution to break free from my workplace admins and start devving Nim with my non administered linux pc (I would prefer linux, but the laptop is so slow)? :D
File hello.nim contents:
proc sayHello() =
echo "Hello World!"
when isMainModule:
sayHello()
Yeah I will. They've just been kinda passive regarding my other sample files sent. In this case without access to non-administered windows pc/laptop I need to somehow compile a windows binary without windows and test, does the virus scanner catch the false positive. Eg.this might take a while! :)
Thank you for your reply!
As it turned out there was nothing special with Nim 1.4 per ce. It seemed that the virus engine had updated without my knowledge at the same time I updated the latest Nim version.
Of course I should've checked that out first, so basically it was my mistake (assumption mother of all f*ck ups and all that). I noticed this when I tested the older Nim compiler and the results were exactly the same.
The problem itself still persists and I have to get the word out to the antivirus provider. Sorry for taking your time.
Hmm it seems that the F-secure fixed the problem sometime after I contacted them. The false alarm seemed to raise it's ugly head only when I was connected to internet and especially when I compiled Nim code from cloud provider (Onedrive). So basically it was some borderline sh*t.
The moral of the story is, don't whine on Nim forum, but contact your virus scanner providers or alternatively break free from your admin masters! :)
> I would prefer linux, but the laptop is so slow
Have you tried using WSL on your Windows 10 laptop ? I've been using it almost exclusively for 2 years now on work issued Windows 10 laptop and it's quite good at giving you a Linux environment inside a Windows machine.
You can even install a GUI environment like xfce, enlightenmen, budgie etc. if you really want the full Linux experience.
One way to see what triggers the alarm is the ol 'malware writers trick' to split the binary into small chunks, then let the antivirus scan. If one file is detected split this file again, let it scan again... until you found the content the antivirus thinks it sees a virus, the change this :).
Maybe this does not work with heuristics but would be a fun experiment.