   [.net] Memory Hardening
  I've heard the term "hardening" when talked about encryption and the likes.  Someone mentioned they can do it to memory, to make it harder for hackers to snoop the running client.I'm going out on the noob limb here, and asking a couple questions?What is it?Can you do it in .NET?Are there some good examples around?Thanks in advance!   
  To my knowledge, such a thing is unfeasible. I imagine it's simply obfuscating memory [like xor-ing a password stored in memory when not in use]. Whatever way it's done it is [again, to my knowledge] always going to be in cleartext while in use, and thus always pretty simple to find for someone determined enough to poke into the app's memory.Since the user has physical access to the computer, they're always going to have access to the app's memory.   ;Quote:Original post by TelastynTo my knowledge, such a thing is unfeasible. I imagine it's simply obfuscating memory [like xor-ing a password stored in memory when not in use]. Whatever way it's done it is [again, to my knowledge] always going to be in cleartext while in use, and thus always pretty simple to find for someone determined enough to poke into the app's memory.Since the user has physical access to the computer, they're always going to have access to the app's memory.True, but it will make poking around in the memory a lot harder. Of course, the first step a hacker/cracker will do is remove the algorythm that's responsible for the "hardening" the memory, and then proceed to treat it like normal memory.It just adds an additional task to the cracker, and will mostly take a few people off the list who are capable of doing so.Toolmaker   ;  The best concept I have seen so far is this: EXECryptorI don't think it is usable for games as it will reduce performance by an order of magnitude. This program doesn't support .NET, but the concept can be applied to .NET executables to, you just need to write a program that does it.   