Frans,
Our obfuscator works differently from other obfuscators on the market. It
generates obfuscated source code that you can recompile, link, and debug
with other assemblies. It includes runtime code source code necessary for
referencing encrypted string data. It factors public member bodies into
obfuscated members and generates stub members to expose the original public
interfaces. It does not reshuffle code or pre-jit since it operates on a
source code level. Nonetheless, the generated obfuscated code is
sufficiently obscure to hide your assembly logic.
The code it produces can be linked directly with non-obfuscated 3rd party
code, and can also be called by your own non-obfuscated code utilizing the
retained exposed public interfaces. Intenal and private members and the
refactored public member bodies are fully obfuscated including calls within
the obfuscated assembly. References to public members in 3rd party
assemblies utilize the public interfaces provided by them.
Jonathan
"Frans Bouma [C# MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Jonathan Pierce wrote:
>
>> "Frans Bouma [C# MVP]" <(E-Mail Removed)> wrote in message
>> news:<(E-Mail Removed)>...
>> > > Oh, your obfuscator obviously produces 100% reliable code,
>> > > I'm sure, but I don't live in dreamland.
>>
>> Yes it does. You should try it before you make assumptions about it.
>
> It would be the first obfuscator being able to do so.
>
>> Our obfuscator generates equivalent obfuscated source code with
>> refactored public members and encrypted literals that you recompile.
>
> No pre-jitted x86 code? No reshuffled code ? you have to if you want to do
> the more advanced obfuscation that you claim to be able to do.
>
>> Each version of Decompiler.NET that we release is decompiled and
>> obfuscated with itself, and then recompiled to produce the version
>> that ships. Most bugs introduced by decompilation or obfuscation would
>> cause the recompiled version of our product to not work correctly, so
>> we would detect them before even releasing the build.
>
> That's not the point. The point is: can reshuffling, prejitting be safe
> for
> 100%? Every obfuscator I tried (on .NET and java) have the same issues:
> code
> obfuscated is sometimes failing in weird situations, often related to 3rd
> party controls in combination with events.
>
> Unless theoretic proof is provided that the code is 100% compatible with
> non-obfuscated code, every vendor obfuscating their work will be required
> to
> retest the obfuscated executable from start to finish.
>
> FB
> --
> Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
> My .NET Blog: http://weblogs.asp.net/fbouma
> Microsoft C# MVP
Similar Threads
