by brainwipe on 4/19/24, 3:57 PM with 2 comments
by brainwipe on 4/19/24, 3:57 PM
ESET deployed the change silently, breaking nodejs implementations and leaving people scrabbling around trying to add node to the SSL scan exception list.
Is it reasonable to expect some warning before a change like this?
I might be forced to choose a replacement. What's your goto brand of antivirus/botnet detection for server and workstation with centralised cloud management?
by DrSiemer on 4/20/24, 12:24 PM
ESET was actually the first thing I suspected, but the feature was hidden so far back that I missed it in earlier disable-all tests.