CODEWITHSUNDEEP
c#obfuscationdeobfuscation
RomaValcer
RomaValcer

Reputation: 2956

Obsfucated variable names

I have code that has replaced function and variable names with Unicode symbols, like \u082. When exported as a project from DotPeek these aren't symbols, but strings like "\u082", thus preventing compiling in Visual Studio 2013. How to fix this issue without manually thinking up some name for everything?

Upvotes: 0

Views: 970

Answers (2)

Yair Nevet
Yair Nevet

Reputation: 13003

You're probably looking at a deliberately obfuscated code that its owners preferred to hide its business logic/algorithms/security etc.

I can't think of an easy way to give the code members names some meaningful identity without to do it manually.

This is the goal of obfuscation process.

Upvotes: 0

Dan Bryant
Dan Bryant

Reputation: 27495

The whole point of obfuscation is that the original names are lost. You could attempt to write a program to make up names based on context, but this would be a fairly challenging endeavor.

In addition, most good obfuscators are going to do other things to the code to make it difficult to understand, possibly even introducing constructs that the runtime allows, but which crash less sophisticated decompilers. Really, though, if you have the rights to use the source code, you should hopefully have access to an unobfuscated copy...

Upvotes: 3

Related Questions