Re: [2.0] Simple Security
Code obfuscation is really the only option in this case but then they can still modify the application via CIL (common intermediate language). It can prevent them from extracting the original source.
There are tons of obfuscators but the problem is most are expensive and/or don't do a good job.
Smartassembly is nice. ($499.00+)
Weakness: the string encryption and strong name are easily broken by smartkill
Dotfuscator is also nice. (Price not displayed so I am guessing very pricey)
Weakness: The string encryption is easily broken. Does not remove namespaces.
There are tons of others but those are the 2 big ones.
Re: [2.0] Simple Security
Im not sure how good it is but vs2008 has a obscure-er built in ( i haven't used it yet)
but that would only prevent someone from reverse enginering your program not unauthrized usage.
if you really wanted it to be a pain in the rump
you could use a combo of looking for network places and a password.
perhaps even call back home ( send and email) and if it doesn't get a reply then it doesn't start something like that.
Re: [2.0] Simple Security
Quote:
Originally Posted by Quasar6
1) Prevent a third party from taking the program and running it on a
Add the HDD serial number in the application license. That will bind
the application to the pc where the license was generated.