From: Zack Weinberg <zackw@panix.com>
To: Paul_Koning@Dell.com
Cc: gcc@gcc.gnu.org, llvmdev@cs.uiuc.edu, libc-alpha@sourceware.org,
musl@lists.openwall.com
Subject: Re: Compiler support for erasure of sensitive data
Date: Wed, 9 Sep 2015 12:58:36 -0400 [thread overview]
Message-ID: <55F0653C.9010903@panix.com> (raw)
In-Reply-To: <8228C31E-7E1F-478C-9352-3908E6256B2C@dell.com>
On 09/09/2015 12:52 PM, Paul_Koning@Dell.com wrote:
> Then again, suppose all you had is explicit_bzero, and an annotation
> on the data saying it's sensitive. Can static code analyzers take
> care of the rest? If so, this sort of thing doesn't need to be in
> the compiler.
The thing that absolutely has to be implemented in the compiler (AFAICT)
is register clearing. I'm undecided as to how *necessary* that is.
There certainly can be a lot of sensitive data in registers (e.g. AESNI
puts an entire AES key schedule in xmm registers). I don't know of any
exploits that depended on salvaging such data from registers, but I
don't follow exploit research closely.
zw
next prev parent reply other threads:[~2015-09-09 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 16:36 Zack Weinberg
2015-09-09 16:39 ` Fwd: " Zack Weinberg
2015-09-09 16:41 ` Zack Weinberg
2015-09-09 16:42 ` Rich Felker
2015-09-09 16:47 ` [musl] " Zack Weinberg
2015-09-09 17:13 ` Rich Felker
2015-09-09 18:48 ` [musl] " Zack Weinberg
2015-09-09 20:05 ` Rich Felker
2015-09-09 16:52 ` Paul_Koning
2015-09-09 16:58 ` Zack Weinberg [this message]
2015-09-09 17:25 ` [musl] " Rich Felker
2015-09-09 17:54 ` David Edelsohn
2015-09-09 18:02 ` Paul_Koning
2015-09-09 18:11 ` David Edelsohn
2015-09-09 19:03 ` Zack Weinberg
2015-09-09 20:26 ` Szabolcs Nagy
2015-10-22 16:02 ` [musl] " Denys Vlasenko
2015-10-22 16:09 ` Denys Vlasenko
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=55F0653C.9010903@panix.com \
--to=zackw@panix.com \
--cc=Paul_Koning@Dell.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=llvmdev@cs.uiuc.edu \
--cc=musl@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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).