No Fucking with Sophos

We run Sophos on all of our machines at work.  I recently built a Windows 10 machine for one of our developers.  He ran into a problem, however, when he tried to debug the application he was writing.

Sophos was falsely blocking his application with the following error message:

File “C:\Users\[username]\Documents\Visual Studio 2015\Projects\KillerFuckingApp\KillerFuckingApp\obj\x86\Debug\intermediatexaml\KillerFuckingApp.exe” belongs to virus/spyware ‘Mal/DotNet-C’.

Ostensibly a false positive I went to discuss the matter.  It didn’t seem likely that his code shared any code with the known exploit so for shits and giggles I asked him to rename the application anything else to see if Sophos was merely objecting to the name.

Sure enough, once he removed “fucking” from the title, Sophos let things be.

At least Visual Studio wasn’t censoring our fucking developer.

Thanks, Sophos; but, you know, fuck off.

Share

Leave a Reply

Your email address will not be published. Required fields are marked *