All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Two interesting papers I've been reading (or, ASLR is not enough)
Date: Sun, 14 Feb 2016 18:33:24 -0500	[thread overview]
Message-ID: <20160214233324.GA28274@thunk.org> (raw)

Perhaps these techniques are well known in the security world (after
all, these papers are 2-3 years old), but I'm just a kernel progammer,
and I don't have time to necessarily keep up with the latest papers
coming out of academia regarding security (it's hard enough keeping up
with all of the papers out from the file system and storage
community!).  As a result, they were eye-opening to me in terms of
what the exploit writers have been working on:

Kevin Snow, Fabian Monrose, Lucas Davi, and Alexandra Dmitrienko.
"Just-In-Time Code Reuse: On the Effectiveness of Fine-Grained Address
Space Layout Randomization".  2013 IEEE Symptosium on Security and
Privacy.
http://www.ieee-security.org/TC/SP2013/papers/4977a574.pdf

Michael Backes, Thorsten Holz, Benjamin Kollenda, Philipp Koppe,
Stefan Nürnberger, and Jannik Pewny.  "You Can Run but You Can’t Read:
Preventing Disclosure Exploits in Executable Code".  CCS 2014.
https://www.infsec.cs.uni-saarland.de/wp-content/uploads/sites/2/2014/10/nuernberger2014ccs_disclosure.pdf

Anyway, maybe this is old news for everyone on the list, but if you
haven't read these papers, IMO they are definitely worth a read.  Does
anyone have a list of interesting security papers that might be of
interest to kernel programmers who want to know what the security
researchers have been up to?

Cheers,

					- Ted

                 reply	other threads:[~2016-02-14 23:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160214233324.GA28274@thunk.org \
    --to=tytso@mit.edu \
    --cc=kernel-hardening@lists.openwall.com \
    /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.