Hi sKip,
I don't want to start any flame so I will only say that we think at packers in two different way.
Quote:
|
Originally Posted by sKip
In fact i had a look at Deploy.NET ver 0.0.2.4 Beta way back in 2003.
What i can say it worked like a Obfuscatpr plus some Encryption/decryption routines.
|
It's not completely true because what you call some enc/dec routines is really a loader that unpacks at runtime the original app and execute it in a different AppDomain. I think this is a packer.
Quote:
|
Originally Posted by sKip
Dotfuscator worked like a packer+protector, too because your project will have less size + Obfuscation.
|
Ok, it has less size but when you decompile protected app, the original source lines are all there (obfuscated but there!) and you can still debug it. So I think this is an obfuscator.
Quote:
|
Originally Posted by sKip
Salamader translates your project.
xenoCode Enterprise has got string encryption, anti-ILDASM-routines, watermarking etc.
|
Sorry but I never played with them... until now...
What I think is that a packer hides completely the original code with encryption routines and it decrypts it at runtime to execute it. An obfuscator instead, uses overload of methods with meaningless names, string encryption, anti-Ildasm, etc. etc. but leaves the source code well visibile with any decopiler/disassembler.