From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] pathetic
Date: Wed, 25 Feb 2004 08:26:01 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0402250822260.9147-100000@maxroach.lanl.gov> (raw)
this is a new "innovation" that is being shown at
http://www.newscientist.com/news/news.jsp?id=ns99994696
" Until now, Intel-compatible processors have not been able to distinguish
between sections of memory that contain data and those that contain
program instructions. This has allowed hackers to insert malicious program
instructions in sections of memory that are supposed to contain data only,
and use buffer overflow to overwrite the "pointer" data that tells the
processor which instruction to execute next. Hackers use this to force the
computer to start executing their own code (see graphic).
The new AMD chips prevent this. They separate memory into instruction-only
and data-only sections. If hackers attempt to execute code from the data
section of memory, they will fail. Windows will then detect the attempt
and close the application.
"Buffer overflows are the largest class of software vulnerabilities that
lead to security flaws," says Crispin Cowan, of computer security company
Immunix in Portland, Oregon.
"
golly. seperate I&D space. Which is an idea that is only about 40 or so
years old (Burroughs 5500 ... or am I late even with that).
Actually I'm puzzled anyway as the segment descriptors on x86 have code
and data bits. I'd be willing to be the real issue is that XP uses the
moral equivalent of self-modifying-code, and that now that XP is being
cleaned up they can actually use those bits. But I'm guessing.
I really love the PC world. The only reason they have not claimed
invention of the wheel is that they don't need it yet.
ron
next reply other threads:[~2004-02-25 15:26 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 15:26 ron minnich [this message]
2004-02-25 15:41 ` Derek Fawcus
2004-02-25 16:02 ` ron minnich
2004-02-26 1:15 ` Derek Fawcus
2004-02-26 3:45 ` ron minnich
2004-02-26 4:12 ` Derek Fawcus
2004-02-26 6:48 ` boyd, rounin
2004-02-26 6:41 ` boyd, rounin
2004-02-25 16:26 ` Aharon Robbins
2004-02-26 6:02 ` boyd, rounin
2004-02-26 10:41 ` Douglas A. Gwyn
2004-02-26 11:32 ` Charles Forsyth
2004-02-26 11:33 ` Geoff Collyer
2004-02-26 12:39 ` Dave Lukes
2004-02-26 12:11 ` boyd, rounin
2004-02-26 13:42 ` dbailey27
2004-02-26 14:36 ` ron minnich
2004-02-26 14:41 ` David Presotto
2004-02-26 14:40 ` dbailey27
2004-02-26 14:47 ` ron minnich
2004-02-26 14:44 ` dbailey27
2004-02-26 15:28 ` ron minnich
2004-02-26 15:38 ` George Michaelson
2004-02-26 16:16 ` ron minnich
2004-02-26 17:32 ` [9fans] SPF+SMTP C H Forsyth
2004-03-01 10:34 ` [9fans] pathetic Vin McLellan
2004-02-26 15:38 ` dbailey27
2004-02-26 14:58 ` andrey mirtchovski
2004-02-26 15:53 ` dbailey27
2004-02-27 9:01 ` boyd, rounin
2004-02-27 10:52 ` Geoff Collyer
2004-02-27 13:07 ` David Presotto
2004-02-27 20:26 ` Lyndon Nerenberg
2004-02-27 22:22 ` Tristan Seligmann
2004-02-27 23:36 ` Geoff Collyer
2004-02-27 13:42 ` Dave Lukes
2004-02-27 15:42 ` a
2004-02-27 17:45 ` 9nut
2004-02-27 23:10 ` boyd, rounin
2004-02-29 21:11 ` boyd, rounin
2004-02-26 15:16 ` C H Forsyth
2004-02-26 15:37 ` Dave Lukes
2004-02-26 17:55 ` jmk
2004-02-26 19:23 ` Richard Miller
2004-02-26 19:35 ` jmk
2004-02-26 19:50 ` Richard Miller
2004-02-27 11:04 ` Dan Moniz
2004-02-26 20:46 ` boyd, rounin
2004-02-26 15:37 ` Derek Fawcus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0402250822260.9147-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).