S
Susan Baker
We are currently developing a commercial application which we are
writing mostly in C# (at least the front end).
The apparent ease at which code is reverse engineered gives me sleepless
nights (I come from a C/C++ background). It appears that signing
assembles and using role based security policies etc have limited
benefits if an end user can easily reverse engineer the binaries and
"side step" any implemented security policies.
I may be over emphasising the problem - but I'd like to know what
measures commercial vendors out there (that use C#), are employing to
ensure that their IP stays as safe as possible?
MTIA
writing mostly in C# (at least the front end).
The apparent ease at which code is reverse engineered gives me sleepless
nights (I come from a C/C++ background). It appears that signing
assembles and using role based security policies etc have limited
benefits if an end user can easily reverse engineer the binaries and
"side step" any implemented security policies.
I may be over emphasising the problem - but I'd like to know what
measures commercial vendors out there (that use C#), are employing to
ensure that their IP stays as safe as possible?
MTIA