Yes, I've toyed around with hacking open an app back in the day. It never was too terribly hard, just a matter of time and how long it took to get bored with it. So, the idea is to make it terribly time consuming. It does not look like relying on the CLR to ensure assemblies have not been tampered is a viable solution.
Thanks, -T > If the hacker has admin access to your box, you are done. If they don't, > you can secure the files on that box via NTFS security. The way I see > it, solving the problem has nothing to do with the CLR. It has > everything to do with configuring the underlying platform. > > In terms of how hard it is to reverse engineer stuff to look for weak > points: it's not too hard. It takes a while, but anyone can learn x86, > and that's the only real skill required. I once hacked a legal copy of > AutoCAD I had just to see if I could do it. Took me about four hours, > and they use a supposedly secure setup where you need to plug an actual > piece of hardware into the machine before the program will run. > > I have a friend that used to compare efforts to secure part of a system > when the foundation was insecure to building a giant castle wall with a > moat in front of it, but leaving a nice flower-lined path up to the back > door, which is made of Nerf. > > You can read messages from the Advanced DOTNET archive, unsubscribe from > Advanced DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
