mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Roel Kluin <roel.kluin@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org
Subject: Re: Is kernel optimized with dead store removal?
Date: Thu, 25 Feb 2010 20:58:01 -0300	[thread overview]
Message-ID: <20100225235801.GE5218@khazad-dum.debian.net> (raw)
In-Reply-To: <19334.40943.479593.304961@pilspetsen.it.uu.se>

On Thu, 25 Feb 2010, Mikael Pettersson wrote:
>  > In the sha1_update() case I don't know whether the stack is recycled and
>  > leaked - it may be dependent on the calling function, but isn't it
>  > vulnerable?
> 
> It's only vulnerable if the data leaks to a less trusted domain.

If it is anything you wanted to protect badly enough that you already have
code to clobber it later, this *is* a security bug.

Not only you remove one layer of security, you also widen a lot the window
of opportunity to, e.g., http://en.wikipedia.org/wiki/Cold_boot_attack

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

      parent reply	other threads:[~2010-02-25 23:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 22:13 Roel Kluin
2010-02-25 11:06 ` Mikael Pettersson
2010-02-25 15:14   ` Roel Kluin
2010-02-25 16:06     ` Mikael Pettersson
2010-02-25 18:24       ` Stefan Richter
2010-02-25 23:58       ` Henrique de Moraes Holschuh [this message]

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=20100225235801.GE5218@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=roel.kluin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®