My software has been cracked
smondrup
Posts: 4
I've been protecting my software with SmartAssembly for just a couple of months, but it has already been cracked. I'm not using the strongest protection, so I'm wondering if it's worth the trouble trying to get my software working with the strongest protection.
I release my software quite often, so I really just need a protection mechanism that's not too easy to break, but if the hackers have ready made tools that can break any program protected with SmartAssembly, then I don't want to go through the hassle of increasing the protection level.
Anyone with experience here? Any advice would be greatly appreciated.
I release my software quite often, so I really just need a protection mechanism that's not too easy to break, but if the hackers have ready made tools that can break any program protected with SmartAssembly, then I don't want to go through the hassle of increasing the protection level.
Anyone with experience here? Any advice would be greatly appreciated.
Comments
SA is a good tool, but the more popular a protection tool is, the more attention it will receive.
You should implement more complex security checks in your programs. Don't rely on a protection tool to do everything for you, implement another blanket of defense.
I know the software will get cracked sooner or later no matter what, but I was just wondering if I would be wasting my time trying to increase the protection level in SA.
Preventing disassembly is the major protection feature to protect your IP and licensing model. Since .NET Intermediate Language is human-readable (although arcane and difficult) it's easier to disassemble back to the original language (VB, C#) than unmanaged Win32 code is. SA helps by mangling method names (so if you have a method called "ConnectDatabase", it will be changed to something less-obvious), rewriting the flow control, and pruning.
I work at Red Gate as a support technician and I have to debug and reverse-engineer software for a living, and I can tell you SA makes it difficult for me. I rely on the exception reporting features to know what went wrong. Since the information about how to decode stack traces and get variable values is all kept on our site, this information is secure against malicious attackers who want to do the same thing.
If you have any information about how, specifically, someone managed to recompile or modify your app, I think I can honestly say that Red Gate would like to know, thanks!
My software has been cracked a few times in the past, which was the main reasons why I started using SA. I really do like your software, since it's easy to use and seems to just work (especially after version 5).
I have not yet found the latest cracked version, so I know I should be careful with what I write, but here are the reasons why I believe my software has been cracked:
1. A user admitted to one of my associates that he purchased a cracked version, but would not reveal where he got it from.
2. My online activity log shows lots of people using the software with non-existing activation keys. This suggest the activation module has been deactivated in the software.
3. I've had the usual post-crack traffic spike on my website.
I've now increased SA protection to maximum level, and everything just seems to work with the latest version. I couldn't set protection to maximum level in previous versions without breaking my software.
If I get hold of the cracked version I'll send it to you together with the original version, so you can take a look at what they've done (I'm assuming it has actually been cracked here, which is of course not a certainty).
I can also send you the un-cracked software now if you're interested, just in case I've left anything exposed (I understand if you don't have time to look at this).
support@red-gate.com
whenever you are ready). We will call to confirm.