Date: | August 20, 2004 / year-entry #313 |
Tags: | other |
Orig Link: | https://blogs.msdn.microsoft.com/oldnewthing/20040820-00/?p=38113 |
Comments: | 5 |
Summary: | Carmen Crincoli covered the interaction between PAE and NX on his own blog, so I'll merely incorporate his remarks by reference. (And notice again the concession to backwards compatibility. Without the backwards compatibility work, XP SP2 would have shipped with NX support and an asterisk, "* and those of you who have device drivers that are... |
Carmen Crincoli covered the interaction between PAE and NX on his own blog, so I'll merely incorporate his remarks by reference. (And notice again the concession to backwards compatibility. Without the backwards compatibility work, XP SP2 would have shipped with NX support and an asterisk, "* and those of you who have device drivers that are not PAE-ready will not be able to take advantage of these new security enhancements. We could've done something to make your systems secure, but we decided not to do it in order to teach you a lesson.") |
Comments (5)
Comments are closed. |
"His"?
Yeah, I’m a guy. Don’t get too hung up on the name, I’m Italian, not Hispanic. :)
What I’ve never figured out is why Intel didn’t use the extra PTE space back when they introduced it with the PPro (it was the PPro, wasn’t it? I can’t remember now).
The need for read-but-not-execute has been plainly obvious since the frigging Morris worm, if not before. As such we can somewhat understand why the 386 has no 3-bit protection (it had to work on small machines and no-one really expected buffer overflows to be so significant), but by the time the PAE came along there was no such excuse. PAE gave us enough room in the PTEs for an NX bit, but Intel didn’t bother.
Carmen: If someone asks, you can aim them at your only (that I know of) famous male namesake.
Why does the index page claim five comments but only 4 appear?