|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
hi,
i use compact frameword and c# to program on pocket pc is there a way to prevent user to examine constant in a .exe using ildasm ? thanks in advance You can't prevent the use of ILDASM, but you can run an obfuscator on your
code to make it harder for someone to understand what it does. Joe K. Show quote "vhoward" <r***@rien.fr> wrote in message news:%23mORVbMLFHA.508@TK2MSFTNGP12.phx.gbl... > hi, > > i use compact frameword and c# to program on pocket pc > > is there a way to prevent user to examine constant in a .exe using ildasm > ? > > thanks in advance > > March 19, 2005
There is no way to restrict ildasm, unless you restrict the NTFS permissions on the assembly itself. This is the only way I can think of. I don't think that solves anything, however, because I assume everybody can view my code after I deploy my application. This is the reason why you shouldn't put any database connection strings or keys in Constants (or anywhere for that matter) in your code. Constants can easily be viewed with reverse engineering. Hope this helps and you can always use an obfuscator to make reverse engineering harder. (and remember "harder" does not mean "secure") Good luck! Joseph MCAD Show quote "vhoward" wrote: > hi, > > i use compact frameword and c# to program on pocket pc > > is there a way to prevent user to examine constant in a .exe using ildasm ? > > thanks in advance > > > > hi, You can obfuscate your app with Spices.Net Obfuscator > > i use compact frameword and c# to program on pocket pc > > is there a way to prevent user to examine constant in a .exe using ildasm > ? > > thanks in advance > (http://spices.9rays.net) with antiILDASM = Complete, this prevents from opening your app in ILDASM and some decompilers. -- Best regards, Al Ponomarev |
|||||||||||||||||||||||