1996-12-19 - Code+Data separation
Header Data
From: ph@netcom.com (Peter Hendrickson)
To: cypherpunks@toad.com
Message Hash: 2e1c9ff7f8a88d21024321b572342f16d8791934a4480232cdeb4a364cd71402
Message ID: <v02140b01aedf4fba9ec3@[192.0.2.1]>
Reply To: N/A
UTC Datetime: 1996-12-19 20:08:33 UTC
Raw Date: Thu, 19 Dec 1996 12:08:33 -0800 (PST)
Raw message
From: ph@netcom.com (Peter Hendrickson)
Date: Thu, 19 Dec 1996 12:08:33 -0800 (PST)
To: cypherpunks@toad.com
Subject: Code+Data separation
Message-ID: <v02140b01aedf4fba9ec3@[192.0.2.1]>
MIME-Version: 1.0
Content-Type: text/plain
Allowing code and data to reside in the same areas of memory is
a nice convenience, but it makes security harder to implement
because it means code is modifiable and data can be created which
just happens to do bad things if it is executed.
Are there any modern processors which keep the code and data separated?
Peter Hendrickson
ph@netcom.com
Thread
Return to December 1996
- Return to “Bill Frantz <frantz@netcom.com>”
- Return to “ph@netcom.com (Peter Hendrickson)”
Return to “Vangelis <vangelis@qnis.net>”
- 1996-12-19 (Thu, 19 Dec 1996 12:08:33 -0800 (PST)) - Code+Data separation - ph@netcom.com (Peter Hendrickson)
- 1996-12-20 (Thu, 19 Dec 1996 18:58:39 -0800 (PST)) - Re: Code+Data separation - Vangelis <vangelis@qnis.net>
- 1996-12-20 (Thu, 19 Dec 1996 21:48:36 -0800 (PST)) - Re: Code+Data separation - Bill Frantz <frantz@netcom.com>