From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Secure update of uboot devices?
Date: Wed, 28 Dec 2011 18:53:53 +0100 [thread overview]
Message-ID: <201112281853.53567.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAB+EkH5DDpfLQqpE9DFQnWLC2M=1af6pFHEumw-mQyC7zGS99A@mail.gmail.com>
> With the new threats like Stuxnet and Duqu one need to improve on how new
> updates to software is distrubuted to devcies so one can
> be sure that it's not a hacked or modified software that runs in the
> device. We use uboot + usb stick to update the software in our devices.
> Have anyone been trying out to add e.g cryptated,certificates or rsa keys
> to uboot?
sha1sum of the file isn't enough?
next prev parent reply other threads:[~2011-12-28 17:53 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 [this message]
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
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=201112281853.53567.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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