dll protect code

  • Thread starter Thread starter Steph
  • Start date Start date
S

Steph

hello,
i want hide my code of my dll...

when you use red gate, you can see all your code...
so... how do for protect my code ?
 
Steph expressed precisely :
hello,
i want hide my code of my dll...

when you use red gate, you can see all your code...
so... how do for protect my code ?
Click to expand...

Search for "obfuscation".

Hans Kesting
 
hello,
i want hide my code of my dll...

when you use red gate, you can see all your code...
so... how do for protect my code ?
Click to expand...

Don't give it to anyone.

For a more detailed discussion, Google this newsgroup for "obfuscation",
"copy protect", etc. as the issue has been hashed out dozens of times
already (complete with real-world reports of bugs cause by obfuscation).

The short answer (from me): no matter what you do to the code, if there's
anything in there worth stealing, either someone will bypass whatever
protection you implement or you spent way too much on the protection for
the value of your code. The only true security is to not deliver the code
to the customer at all (which is not as facetious a suggestion as you
might think).

Pete
 
Peter said:
Don't give it to anyone.

For a more detailed discussion, Google this newsgroup for "obfuscation",
"copy protect", etc. as the issue has been hashed out dozens of times
already (complete with real-world reports of bugs cause by obfuscation).

The short answer (from me): no matter what you do to the code, if
there's anything in there worth stealing, either someone will bypass
whatever protection you implement or you spent way too much on the
protection for the value of your code. The only true security is to not
deliver the code to the customer at all (which is not as facetious a
suggestion as you might think).

Pete
Click to expand...


hum ok... but when you sale your .exe ... your DLL ... etc ... nothing
is protect in .NET !
you can user redgate reflector (example) for retrieve all code line !!!!
 
It's easier with .NET but even in the past you had tool such as "Sourcer"
that could be used to decompile machine code and perhaps even create a C
source file If I remember...

Either obfuscate but by design compiled code has to be understood by the
computer (and then someone with enough motivation will be able to understand
what the code is doing).
 
hum ok... but when you sale your .exe ... your DLL ... etc ... nothing
is protect in .NET !
Click to expand...

That is true no matter how you wrote your code. It is simply not possible
to allow your code to be run on a computer outside your own control and
still prevent someone from inspecting your code.
you can user redgate reflector (example) for retrieve all code line !!!!
Click to expand...

Reflector makes it a bit easier is all. If you think it makes such a huge
difference, then just code your "sensitive" parts as unmanaged code (e.g.
native compiled C++...if you like, using COM might make it a little
simpler to then use from .NET). It's still a waste of time, but at least
any bugs will be your own.

Pete
 
Back
Top