No, execution protection actually is a good feature. It' meant for mapping memory adresses which are used only for data and not for program-code as non-executable, thus preventing the nowadays most common security-hole used for worms/viruses: the use of buffer-overflows to execute foreign code on another machine.
If the memory adress is mapped as non-executable, even after a buffer-overflow, the CPU won't execute the "hostile" program-code. Unfortunately not only the OS has to support this (WinXP SP2 will introduce it) but also the CPU. AMDs newest CPU support this feature, Intels seem to not do this up to now.
If the memory adress is mapped as non-executable, even after a buffer-overflow, the CPU won't execute the "hostile" program-code. Unfortunately not only the OS has to support this (WinXP SP2 will introduce it) but also the CPU. AMDs newest CPU support this feature, Intels seem to not do this up to now.
Comment