search

mkaring / ConfuserEx

An open-source, free protector for .NET applications
https://mkaring.github.io/ConfuserEx/
MIT License
2.26k stars 349 forks source link

ConfusedBy is seen. #537

Closed bolt-b closed 12 months ago

bolt-b commented 12 months ago

Hello everyone,

Used ILSpy to see how has been changed confused library. What is really seen before and after. What I've seen first when confused lib was added to ILSpy is attached below. Seems it is good hint to those who need to know what was used for confusing. So, how to turn off this hint?

ConfusedBy

sunnamed434 commented 12 months ago

Not sure if it can be disabled, but simply remove the attribute using dnSpy

mkaring commented 12 months ago

The watermark can be removed by the rules. More details about this, can be found here: Watermark - ConfuserEx Wiki

bolt-b commented 12 months ago

The watermark can be removed by the rules. More details about this, can be found here: Watermark - ConfuserEx Wiki

That's the point, the watermarking was not selected at all. The only kind of protection was used, it's renaming. As it is shown below. So, I have no clue which way the watermarking has been enabled in this particular case.

rule

mkaring commented 12 months ago

Please read the "remarks" part of the wiki page. The watermark is enabled by default and needs to be removed explicitly.

bolt-b commented 12 months ago

Please read the "remarks" part of the wiki page. The watermark is enabled by default and needs to be removed explicitly.

Sorry, so, where do I need to put this line? I don't understand.

<protection id="watermark" action="remove" />

mkaring commented 12 months ago

Either in the rule file you save, or you add it to the rules you showed in the in the screenshot above, add the "watermark" rule and switch the first combobox in the line to "remove".

bolt-b commented 12 months ago

Either in the rule file you save, or you add it to the rules you showed in the in the screenshot above, add the "watermark" rule and switch the first combobox in the line to "remove".

I confused a bit with how Confuser is working. :) Based on your post above. If I nothing "removed" as you described above, does it mean that all confusing methods will be applied? In other words, if I want to use "renaming" only. I should add it. It is understandable. What about other methods? Should I leave them as is (don't touch them)? Or should I "remove" them, the way you described above?

TooMuchBlue commented 12 months ago

What about other methods. Should I leave them as is? Or should I "remove" them?

It varies by protection. Many protections are only used if you enable them. However, once you enable them, they may include some default behaviors that you don’t want, and you would need to disable or “dial down” those features to the level you need.

For example, the “constants” protection is disabled by default. If you enable “constants” it will default to compressor=”LZMA”. If you do not want compression of constants, you would need to disable this particular feature.

There are too many variations like this to explain via email. The documentation is your friend. https://github.com/mkaring/ConfuserEx/wiki/Documentation > Protections

github-actions[bot] commented 11 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.