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 🤷
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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: