public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Does U-boot support ASLR?
Date: Thu, 9 Feb 2012 13:28:07 -0600	[thread overview]
Message-ID: <4F341E47.9010306@freescale.com> (raw)
In-Reply-To: <201202091358.54739.vapier@gentoo.org>

On 02/09/2012 12:58 PM, Mike Frysinger wrote:
> On Thursday 09 February 2012 13:37:15 Jason Markley wrote:
> 
> please don't top post, and keep the mailing list in cc
> 
>> I agree any proposal would need to be accompanied by good reasoning.
>> I'm honestly a little confused as to why a generally accepted security
>> feature such as ASLR would NOT be useful for u-boot.  U-boot has the
>> capability to interact with the outside world via the network as well as
>> the console.  When using the U-boot API, it also remains resident in
>> memory.  Wouldn't something like ASLR enhance the security posture of
>> U-boot in those situations?
> 
> u-boot is running in supervisor mode / ring 0 / etc...  you have full access 
> to the hardware with a simple `mw` command.  randomizing the address base of 
> u-boot doesn't gain you anything.  so no, i see no advantage of u-boot itself 
> utilizing ASLR regardless of what it interacts with.

This assumes that the full command line interface is enabled, and is the
mechanism of interaction in question.  It doesn't apply to interactions
over the network, special serial protocols, etc.

> ignoring this, there are two fundamental issues with ASLR:
>  - this early on, u-boot has very little (if no) entropy, so any attempts to 
> generate random numbers are going to be fairly predictable

This doesn't apply if there's a hardware random number generator -- and
even poor entropy is more effort to guess than a fixed address.

>  - scripts that u-boot runs at boot time often times need a chunk of memory to 
> load and boot stuff out of.  if u-boot could randomly be in the middle of that, 
> then your board now randomly fails to boot.  the only way around that would be 
> to have u-boot do virtual addresses, and that's clearly a non-starter.

You'd just need to document which areas U-Boot could be in, and which
areas are free for user use.

It probably doesn't make sense as default behavior, but I could see it
being useful in some situations.

-Scott

  reply	other threads:[~2012-02-09 19:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 14:47 [U-Boot] Does U-boot support ASLR? Jason Markley
2012-02-09 15:13 ` Wolfgang Denk
2012-02-09 15:59   ` Mike Frysinger
     [not found]     ` <4F34125B.9070802@cisco.com>
2012-02-09 18:58       ` Mike Frysinger
2012-02-09 19:28         ` Scott Wood [this message]
2012-02-09 19:50           ` Mike Frysinger
2012-02-09 20:03             ` Jason Markley
2012-02-09 20:06             ` Scott Wood
2012-02-09 20:34               ` Mike Frysinger
2012-02-09 20:54                 ` Jason Markley
2012-02-09 19:55           ` Jason Markley
2012-02-09 20:31             ` Mike Frysinger
2012-02-09 22:16               ` Graeme Russ
2012-02-09 23:08                 ` Jason Markley
2012-02-10  0:09                   ` Graeme Russ
2012-02-10 11:44                   ` Wolfgang Denk
2012-02-09 19:56           ` Jason Markley
     [not found]   ` <4F33E93E.5070804@ggsg.cisco.com>
2012-02-10  7:07     ` Wolfgang Denk
2012-02-10 13:47       ` Jason Markley
2012-02-10 14:23         ` Wolfgang Denk

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=4F341E47.9010306@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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