1996-12-19 - Re: Code+Data separation

Header Data

From: azur@netcom.com (Steve Schear)
To: cypherpunks@toad.com
Message Hash: d8f4972deb0becf8e225632a95dd39c92595301bf7629b82e75c9147a47b283e
Message ID: <v02140b00aedf640e2ed6@[10.0.2.15]>
Reply To: N/A
UTC Datetime: 1996-12-19 21:20:10 UTC
Raw Date: Thu, 19 Dec 1996 13:20:10 -0800 (PST)

Raw message

From: azur@netcom.com (Steve Schear)
Date: Thu, 19 Dec 1996 13:20:10 -0800 (PST)
To: cypherpunks@toad.com
Subject: Re: Code+Data separation
Message-ID: <v02140b00aedf640e2ed6@[10.0.2.15]>
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

I believe those that follow a Harvard architecture do this.

-- Steve







Thread