Isn’t that a matter of behavior? The crack is doing something expected from a crack and the system warns you because most wouldn’t use it without being aware. If you really trust the file, add it as an exception.
Or do you want a software that can vet good cracks from bad cracks?
But you generally want that crack to do something to an executable. Do antivirus etc. tools just heuristically flag everything that looks like it modifies an executable? Lots of legitimate dev tools do that too, so it seems like it’d give a lot of false positives, but I haven’t used Windows in ages so 🤷
Well, how is the system supposed to know that you want the crack to do something to that executable? The anti virus just sees something is happening and flags it. It does not see a difference.
I definitely get what you mean, I just have no idea if antivirus tools flag anything that looks like it modifies executables. My edit to the comment you’re replying to may not have propagated to your instance yet, so here’s what I added:
Do antivirus etc. tools just heuristically flag everything that looks like it modifies an executable? Lots of legitimate dev tools do that too, so it seems like it’d give a lot of false positives, but I haven’t used Windows in ages so 🤷
Isn’t that a matter of behavior? The crack is doing something expected from a crack and the system warns you because most wouldn’t use it without being aware. If you really trust the file, add it as an exception.
Or do you want a software that can vet good cracks from bad cracks?
I think the point is that it’s a bit silly to classify cracks as malware
Cracks modify executables…classic malware/virus behaviour. Almost the definition of malware.
Which is why windows uses a file protection system since at least XP
Enterprise antivirus products have had PUP (Potentially Unwanted Program) category forever. Seems its categorized as “HackTool” so not malware.
Not at all, a crack does something to an executable file that you use. Malware would do the exact same thing.
But you generally want that crack to do something to an executable. Do antivirus etc. tools just heuristically flag everything that looks like it modifies an executable? Lots of legitimate dev tools do that too, so it seems like it’d give a lot of false positives, but I haven’t used Windows in ages so 🤷
Well, how is the system supposed to know that you want the crack to do something to that executable? The anti virus just sees something is happening and flags it. It does not see a difference.
I definitely get what you mean, I just have no idea if antivirus tools flag anything that looks like it modifies executables. My edit to the comment you’re replying to may not have propagated to your instance yet, so here’s what I added: