search

divyang4481 / obfuscar

Automatically exported from code.google.com/p/obfuscar
0 stars 0 forks source link

Obfuscar cannot process itself #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download current release
2. Create a copy of the dll's and exe
3. Run Obfuscar (config file attached)

What is the expected output? What do you see instead?
Break upon saving. Seems to break on C5.dll

What version of the product are you using? On what operating system?
1.3.0 on WindowsXp, MS.Net 2.0

Original issue reported on code.google.com by skolima on 6 Sep 2007 at 3:00

Attachments:

GoogleCodeExporter commented 9 years ago 
I can verify the problem.  It does appear to be a problem with obfuscating 
C5.dll; if
it is removed from the config file, everything appears to work fine.  Will
investigate further.

Original comment by drcfor...@gmail.com on 6 Sep 2007 at 3:15

GoogleCodeExporter commented 9 years ago 
Processing only Obfuscar.exe produces a working program. Touching Cecil.dll 
works,
but the output does not work. Would you like some unit tests with this?

Original comment by skolima on 6 Sep 2007 at 3:16

GoogleCodeExporter commented 9 years ago 
If it can be simplified dramatically (i.e., something much smaller than C5.dll 
or
Mono.Cecil.dll), it would be helpful...otherwise, it's not difficult to 
reproduce the
problem under the debugger with the actual assemblies and your config file.

Original comment by drcfor...@gmail.com on 6 Sep 2007 at 4:03

GoogleCodeExporter commented 9 years ago 
After further investigation, it looks like using cecil from SVN, it works 
properly,
except for assembly signing.

I can put out another release with the latest cecil, but obfuscar still won't 
be able
to obfuscate itself, because both C5.dll and Mono.Cecil.dll have strong names, 
and
obfuscating them breaks the signature.

I think I should add a warning / error message to make this more clear.

Original comment by drcfor...@gmail.com on 6 Sep 2007 at 5:21

GoogleCodeExporter commented 9 years ago 
In r36, dropped in the latest Mono.Cecil.dll, added the error message, and 
bumped the
version number to 1.3.1.

Original comment by drcfor...@gmail.com on 6 Sep 2007 at 9:11