Mass Effect 3 Discussion
Data Execution Prevention (known on other systems as the NX bit) is a protective measure against buffer overflows. It works by marking privileged areas in memory with the NX marker (No eXecute) which prevents these memory areas from executing code from any account that is not part of the NT_AUTHORITY family of users (and it is near impossible to log into these accounts and have them do stuff). This prevents exploits based off of buffer overflows and stack smashing since the intended code the attacker needs to execute to do whatever will never execute because the OS is instructed at the hardware level to never let it happen. Poorly coded software that isn't malicious can often trigger false positives with this scheme.
The end result is that instead of being exploited, Windows will immediately kill the offending process and notify you of the incident. Under Linux, it will most likely appear as a violation under SE Linux and the front end application for that will notify you.
[Edited by Neo7, 3/13/2012 7:26:34 AM]
Thanks for the detailed explanation, that was informative. If you have a good AV program and are very careful with what you allow would you still need something like this?
They still lingered on my system afterwards since when it did try to exploit the specific point, it wound up crashing since it wasn't programmed to be able to handle that scenario (and the cleanup process to hide it's track never executed). One fresh install to Windows 8 (using backups) and found that those malware were still there (although dead at that point).
[Edited by Neo7, 3/13/2012 9:00:04 AM]
Might have to check it out then, thanks. I've never had any problems but you can't be too careful these days.
* Updated game trainers and cheats daily
* Get notified when new cheats are added
* Request which games get new trainers
* Priority support with any problem
• Unlimited Health
• Squad Health
+ 18 more options