From: "Justin R. Smith" <jsmith@mcs.drexel.edu>
To: selinux@tycho.nsa.gov
Subject: A notion
Date: 02 Oct 2001 04:42:53 -0400 [thread overview]
Message-ID: <1002012173.1248.12.camel@vorpal> (raw)
It occurred to me that custom versions of software can be more secure
than standard versions because various exploits (like stack smashing,
etc.) require precise knowledge of certain sizes and distances in RAM
(for instance, the distance from the end of a buffer to the return
point...).
Isn't it possible to develop a "randomizing C compiler" that randomly
varies these distances every time it compiles a program? No two compiles
of the same source code would be exactly the same (but they would
execute the same way).
This might involve inserting small random-sized blocks of dead code, or
doing returns from subroutines through a level of indirection (i.e.,
putting the actual return at some random location in the object code
with a branch to it).
Done right, this might not degrade performance significantly.
--
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2001-10-01 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 8:42 Justin R. Smith [this message]
2001-10-01 21:35 ` A notion Jose Nazario
2001-10-01 22:47 ` Phillip H. Zakas
2001-10-01 22:43 ` Phillip H. Zakas
2001-10-01 23:58 ` Javier
2001-10-02 2:40 ` Conan Callen
2001-10-02 12:05 ` Russell Coker
2001-10-02 12:19 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 23:46 Tim Hollebeek
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=1002012173.1248.12.camel@vorpal \
--to=jsmith@mcs.drexel.edu \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.