protected exe is not working

Question

0.00/5 (No votes)

See more:

C#

I have protected exe by Eazfuscator.net 3.1 on 32bit operating system but it is open on 64bit in ILDisassembler.

Why?

Posted 4-Oct-11 21:41pm

Member 7909353

Updated 4-Oct-11 22:19pm

v4

Add a Solution

Comments

André Kraak 5-Oct-11 3:50am

Edited question:
Removed unnecessary tags

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2011-10-04T21:55:00

Solution 1

Yes? Obfuscation does not stop you opening the exe - nothing will do that as the system needs to be able to read teh file content in order to execute the program.

What obfuscation does is to make it harder (or hopefully a lot harder) to understand the program and reverse engineer it. How hard depends on the obfuscator used and the various options it allows you to apply.

Posted 4-Oct-11 21:55pm

OriginalGriff

Comments

Mehdi Gholam 5-Oct-11 4:01am

In a nutshell, my 5!

Sergey Alexandrovich Kryukov 11-Nov-11 2:21am

Correct! a 5.
--SA

Pete O'Hanlon · Answer 2 · 2011-10-05T01:06:00

The key thing to remember is that IL is a representation of the byte code that .NET uses when it is executing and compiling your application at runtime. Yes, I did just say compiling - .NET optimises and compiles to native while the application is running. Effectively the following steps happen:

You compile your high level code
This creates Common Intermediate Language code
The CIL code is converted into a .NET assembly as bytecode
When the application executes, the bytecode is JIT compiled and this JITed code is executed.

This effectively means that you can reverse your executable (and yes, DLLs are a special form of executable as well). All that obfuscation does is make it harder for somebody to reverse engineer your code through things like variable renaming, etc.