Prev: Calling FindResource to detect the TYPELIB resource in a COMserve
Next: Retrieving ProductID via MSI.dll
From: John Whitworth on 10 Jan 2010 15:08


"James Hahn" <jhahn(a)yahoo.com> wrote in message
news:#G3dAYdkKHA.2164(a)TK2MSFTNGP02.phx.gbl...
> You don't have to obfuscate. If it's just a sequence of numbers you can
> disguise it in many ways. Just try to separate the storage from the
> processing

How exactly would that be done? Is it as simple as storing values in a
module, rather then in a form or a class, for instance?

Thanks

JW

From: mayayana on 10 Jan 2010 17:22
> You don't have to obfuscate. If it's just a sequence of numbers you can
> disguise it in many ways.

Not really. I used to do that, using a function
to calculate an activation number in a native
code executable. Within 24 hours a teenager
in Thailand would have posted a working code. :)

Having it visible as bytes is not good. And the
fact that .Net is not really compiled doesn't help.
But the crackers like a challenge and they can reverse
engineer just about anything by watching the
actions taken in code. Most people won't do that,
but most people don't have to. The codes get
posted online.

A better method, in my experience, is to use
some kind of activation code but also use a
separate EXE for the full version. The crackers
don't want to host downloads. If your trial version
is inherently limited in some way and won't accept
a code then the only way to crack it is to edit the
file and then redistribute either that whole file or
a "custom cracking program".



From: Gregory A. Beamer on 11 Jan 2010 11:51
"Rob" <robc1(a)yahoo.com> wrote in
news:cuWdnYx09654MdXWnZ2dnUVZ_uSdnZ2d(a)giganews.com:

> Ok i see, same website... obfuscator...

Good option, and there are good ones out there. I personally like CodeVeil.
There are also some that will produce truly native code, if you want that
option.

As I mentioned before, there is no way to protect your app from 100% of the
hackers, as really good hackers get down to the assembly level. You can
limit exposure and obfuscation is a good way to go as a first step.

There are some good third party licensing products out there. The
professional hackers will still get through, eventually, but they stop the
run of the mill hack, which is your primary concern.

Peace and Grace,

--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************
From: LogicNP on 15 Jan 2010 00:43
Sure, its quite easy to decompile .Net apps using free tools such as
Reflector. You need to use an obfuscator on your assemblies. Take a look at
Crypto Obfuscator (http://www.ssware.com/cryptoobfuscator/obfuscator-net.htm)
for one such obfuscator. For generating cryptographic licenses for your app
with activation, normal, trial codes, take a look at its companion
CryptoLicensing
(http://www.ssware.com/cryptolicensing/cryptolicensing_net.htm).


First  |  Prev  | 
Pages: 1 2
Prev: Calling FindResource to detect the TYPELIB resource in a COMserve
Next: Retrieving ProductID via MSI.dll