Hi!
> The 386 and up supports no-exec, but only on differing segments. Most OS
> systems aren't properly implemented on the 386+ architecture. The 386+
> supports read-only pages in the paging architecture, but to separate
> executable code from stack and data, you have to point the segment
> registers at differing memory areas. If they overlap, which simplifies
> memory management, then the code, data and stack are all shared. An
> entire segment, according to the Intel documentation, can set aside as
> non-executable.
It not only simplifies code, it also makes it faster. Segments are
obsolete, and intel knows that.
Pavel
--
I'm really [EMAIL PROTECTED] Look at http://195.113.31.123/~pavel. Pavel
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
- Re: WordPad/riched20.dll buffer overflow Gerardo Richarte
- Re: WordPad/riched20.dll buffer overflow Gerardo Richarte
- Re: WordPad/riched20.dll buffer overfl... pedward
- Re: WordPad/riched20.dll buffer o... Christopher Rhodes
- Re: WordPad/riched20.dll buff... Glynn Clements
- Re: WordPad/riched20.dll buff... Jason Spence
- Re: WordPad/riched20.dll buff... Crispin Cowan
- Re: WordPad/riched20.dll buff... Glynn Clements
- Re: WordPad/riched20.dll buff... Solar Designer
- Re: WordPad/riched20.dll buff... Casper Dik
- Re: WordPad/riched20.dll buff... Pavel Machek
- Re: WordPad/riched20.dll buffer overflow User SCOTT
- Re: WordPad/riched20.dll buffer overflow - Full De... Solar Eclipse
- Re: WordPad/riched20.dll buffer overflow Bronek Kozicki
- Re: WordPad/riched20.dll buffer overflow Ussr Labs
- Re: WordPad/riched20.dll buffer overflow Thomas Dullien
- Re: WordPad/riched20.dll buffer overflow Ussr Labs
