From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Secure update of uboot devices?
Date: Fri, 6 Jan 2012 14:25:52 -0500 [thread overview]
Message-ID: <201201061425.52983.vapier@gentoo.org> (raw)
In-Reply-To: <CAB+EkH5g3ybYSLGYtBkATEFVG_WzeSYC3K0SmFOG4436Dr6uXA@mail.gmail.com>
On Friday 06 January 2012 06:24:50 Andreas B?ck wrote:
> Actually there seams to exsist some very old patches for this
> http://lists.denx.de/pipermail/u-boot/2006-September/016960.html
>
> Here a paper quite exact what I am after:
> http://elinux.org/images/2/28/Trusted_Boot_Loader.pdf
>
> Is there any toughts on integating this in trunk or should I try to merge
> this patch with the git trunk of my own?
i think you need to outline exactly what it is you're trying to do. "secure
update" and "secure boot" is way too vague. for starters, you need to outline
the vectors you're trying to protect against. the arm trustzone whitepaper is
a pretty good example of things:
http://infocenter.arm.com/help/topic/com.arm.doc.prd29-genc-009492c/PRD29-
GENC-009492C_trustzone_security_whitepaper.pdf
there are many hardware solutions out there for verifying the integrity of u-
boot itself before executing it, but they tend to be SoC/arch specific. the
trusted boot paper you referred to for example really only makes sense on x86
based platforms.
the patch you referred to however is for verifying the integrity of the kernel
image that u-boot boots. it doesn't help with u-boot itself.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120106/9fb93b3f/attachment.pgp>
next prev parent reply other threads:[~2012-01-06 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 7:58 [U-Boot] Secure update of uboot devices? Andreas Bäck
2011-12-28 17:53 ` Marek Vasut
2011-12-30 12:13 ` Andreas Bäck
2011-12-30 12:37 ` Wolfgang Denk
[not found] ` <CAB+EkH69iuEjcdKUYeX2NDw_v5bDJ6aLBbLPUN7ii7dnnAQmsg@mail.gmail.com>
2012-01-02 10:06 ` Wolfgang Denk
2012-01-06 11:24 ` Andreas Bäck
2012-01-06 19:25 ` Mike Frysinger [this message]
2012-01-06 23:20 ` Wolfgang Denk
2012-01-06 23:56 ` Kim Phillips
2012-03-17 9:25 ` Andreas Bäck
2013-01-08 21:15 ` Simon Glass
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=201201061425.52983.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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