From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] What methods of software authentication does U-Boot support?
Date: Fri, 18 Apr 2008 16:32:11 -0500 [thread overview]
Message-ID: <20080418163211.d5a1ee64.kim.phillips@freescale.com> (raw)
In-Reply-To: <AA28F077645B324881335614E4F7C428034CCB@win-ex01.bench.com>
On Fri, 18 Apr 2008 12:01:38 -0500
<Ken.Fuchs@bench.com> wrote:
> Goal:
>
> U-Boot will run only software that has been
> authenticated to be from the system's producer.
>
> --- A Potential Authentication Method ---
>
> The producer of the system generates a cryptographic
> [private-key, public-key] pair, storing the public-key
> on the same media as U-Boot (i.e. NOR flash; perhaps
> as a read-only environment variable) on all systems
> and keeping the private-key hidden at a secure site.
> A hash of the software is generated, encrypted
> with the private key and shipped with the software.
>
> U-Boot reads the private-key encrypted hash and decodes
> it with its public-key. U-Boot loads the software and
> generates the hash. If both hashes match, the software
> is authenticated and U-Boot executes the authenticated
> software.
>
> --- Comment ---
>
> U-Boot obviously supports loading and verification of
> the generated hash, but I haven't been able to locate
> public-key cryptographic or other authentication support
> in U-Boot. Perhaps, it is available as a loadable
> (stand-alone) module?
>
> Any comments or suggestions?
>
this patch taps into openssl:
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/23977
or you might want to reuse some of linux' crypto library code.
Kim
next prev parent reply other threads:[~2008-04-18 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 17:01 [U-Boot-Users] What methods of software authentication does U-Boot support? Ken.Fuchs at bench.com
2008-04-18 21:32 ` Kim Phillips [this message]
2008-04-20 23:32 ` Wolfgang Denk
2008-04-21 12:07 ` Kenneth Johansson
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=20080418163211.d5a1ee64.kim.phillips@freescale.com \
--to=kim.phillips@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