search

christopherdebow1 / obfuscar

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

New option to choose obfuscation naming #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Option to choose obfuscation naming 

a) a-z / A-Z (already by default)
b) unprint characters (chr(1) - chr(31))

Original issue reported on code.google.com by pipisc...@gmail.com on 17 Feb 2010 at 11:18

GoogleCodeExporter commented 8 years ago 
The problem with unprintable characters is that stack traces become unreadable 
and in
most projects you need a way to analyze stack traces (with the use of the 
mappings
file) in case your app crashes.

Original comment by webbi...@gmail.com on 1 Mar 2010 at 8:39

GoogleCodeExporter commented 8 years ago 
My fork at https://github.com/lextm/obfuscar/ has accumulated patches from 
others that enable using Unicode chars or Korean chars as new naming styles.

It is also possible to use chr(1) - chr(31) but it won't give obfuscated result 
more protection. Thus, I will not implement this in my fork.

Note that the best way to debug an issue is still to use the obfuscated 
assembly with default chars. So you might consider,

* Ship a production assembly obfuscated with Unicode or Korean chars.
* When end users meet issues, send them a default chars obfuscated assembly for 
debugging purpose.

Original comment by lextu...@gmail.com on 28 Apr 2013 at 7:19