.NET obfuscation: how is it done, how safe is it?

Question

I raised the question of obfuscation in another question that someone answered: "Obfuscation does not stop."

Instead of starting the discussion in the comments, I wanted serious community responses to how safe my code is when it gets messy with the obfuscator X, Y or Z, and if any obfuscation tools really do the job.

I am also interested in any explanations that are given to get a general idea of ​​how the obfuscator works.

From my understanding, obfuscation cannot prevent reflection and detection methods, etc., but it makes the code inside the methods less understandable with the help of top variable names. It is not right? What else is he doing?

Answer 1

Obfuscation can never be truly safe, as you can always look at MSIL. Even with a good obfuscator, people could play most of your code simply from MSIL, and since you have no choice but to compile MSIL, you really can't do anything.

Answer 2

There are ways to do such things - for example, have you ever tried using Reflector on yourself?

, , , , , - . - , - , . , , .

, , . , ,.NET .

Answer 3

— .

Answer 4

- , , , . , Joel Coehoorn .NET- :

. , . , , - .

Obfuscation, , , :

. . Obfuscate Obfuscate

Answer 5

, ISSA "" , Java .NET" - PDF, . , , .