logoalt Hacker News

asveikautoday at 4:27 PM3 repliesview on HN

The heuristics powering this, as well as the Windows Defender whitelisting, are terrible.

My understanding is that a specific binary needs to become popular for it to stop being flagged. This creates a chicken and egg problem. Users are not incentivized to use the program with the warning. But removing the warning requires many people to ignore the warning.

This is a big problem for anyone writing Windows software. An indie developer or small open source project is not going to do well with this.


Replies

grueztoday at 5:02 PM

>My understanding is that a specific binary needs to become popular for it to stop being flagged. This creates a chicken and egg problem.

Given the recent npm axios compromise this sounds like a pretty smart move?

show 2 replies
whateverboattoday at 6:37 PM

This is also happening on linux for me.

show 1 reply
Frotagtoday at 4:49 PM

Conveniently M$ lets you buy a signing certificate to fix this.

https://stackoverflow.com/questions/48946680/how-to-avoid-th...

show 2 replies