New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Obfuscated names question #1359

Closed
greenozon opened this Issue Dec 25, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@greenozon
Copy link

greenozon commented Dec 25, 2018

ILSpy version 4.0.0.4472-beta3

question: are there any plans to translate (make visible) obfuscated namespaces/classes/methods/types/etc inside the tool?

to be more specific, the question is all about just to properly visualize, not do any real conversions/renames/etc

as for the moment there are two parts:
in the left tree these are not visible at all
in the right pane some symbols grayed out are being printed out

example:

screenshot_31

Expected behavior: consider some scheme of translating (just for visual perception of end-user) of invisible names

Example of possible solution (translating invisible (unicode) chars into \u1234 - it takes more display footprint, but at least one might work with it/analyze/navigate/etc

screenshot_34

@siegfriedpammer

This comment has been minimized.

Copy link
Member

siegfriedpammer commented Dec 29, 2018

There are two possible solutions:

  1. Implement the escape sequences as transformation when loading the module into the type system.
  2. Add transformations on top of the decompiler and in the UI.

I would prefer the first, because otherwise it is easy to miss something.

@greenozon

This comment has been minimized.

Copy link
Author

greenozon commented Dec 29, 2018

Thank you for you interest and response
From end-user perspective - any option would be fine :)
as the goal is read-ablity as well as click-ability and navigation

@lextm

This comment has been minimized.

Copy link
Contributor

lextm commented Feb 17, 2019

Usually you can run de4dot before opening the assembly in ILSpy, https://github.com/0xd4d/de4dot IMHO ILSpy shouldn't attempt to do anything special for obfuscated assemblies.

@greenozon

This comment has been minimized.

Copy link
Author

greenozon commented Feb 17, 2019

Of course, de4dot to the rescue, but it does not cover 100% of use cases.
Very often you need to peek into input assembly to understand some tidbits
and you can't
see my pics above why

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment