Protecting IL Code
From: YK (YK_at_discussions.microsoft.com)
Date: 06/30/04
- Next message: Cor Ligthert: "Re: re:Server Explorer: Only for SQLSrv/MSDE?? (Kevin Yu)"
- Previous message: YK: "Protecting IL Code"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 23:45:02 -0700
All,
What is the best way to protect IL code?
---------------------------------------------------
Typical scenario:
Visual Studio .NET 2003 includes Dotfuscator Community Edition, which intends to protect IL code. However, many .NET applications use data binding in UI forms. For example:
Employee e = new Employee();
txtName.DataBindings.Add("Text", e, "Name");
txtAddress.DataBindings.Add("Text", e, "Address");
In this scenarion, property names are coded as string to be resolved at runtime. After obfuscation, the property names in the Employee class have changed, but the string in the data binding code retained.
We can configure obfuscator tool with a list of exception names that the tool will not process. However, this maintains the property names, which eventually reveal the actual logic.
------------------------------------------
Thanks
-YK
- Next message: Cor Ligthert: "Re: re:Server Explorer: Only for SQLSrv/MSDE?? (Kevin Yu)"
- Previous message: YK: "Protecting IL Code"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|