public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Secure booting
Date: Thu, 13 Feb 2014 09:35:30 +0100	[thread overview]
Message-ID: <52FC83D2.80106@denx.de> (raw)
In-Reply-To: <CAE0zQkuLwALLhbVZgBLPj_WYnWbO=E_nXg4K8Zx9N70n4d0BVw@mail.gmail.com>

Hello JYOTI,

Am 13.02.2014 08:42, schrieb JYOTI DUBEY:
> Can I obtain information as how secure booting works.How the keys and
> certificates are generated and also encryption and decryption steps
> involved in the authentication process. i would like to know just the
> theory behind it not and commands or technical details.
> I have attached pictorial representation of 3 consecutive steps involved in
> secure booting but while I tried to understanding the working though the
> diagram I felt that authentication might never succeed as no decryption is
> taking place.Can anyone please inform how the steps are taking place? I
> have also attached the documentation related to high assurance booting.

Maybe this 2 documents in the u-boot source help you:

u-boot:doc/uImage.FIT/signature.txt
u-boot:doc/uImage.FIT/verified-boot.txt

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2014-02-13  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  7:42 [U-Boot] Secure booting JYOTI DUBEY
2014-02-13  8:35 ` Heiko Schocher [this message]
2014-02-15 19:32 ` Simon Glass
  -- strict thread matches above, loose matches on Subject: below --
2014-03-16  3:39 JYOTI DUBEY
2014-03-17  3:55 ` Simon Glass
     [not found]   ` <CAE0zQksZ0+0vCNGoTPbdYKOCgxkyXP8ZgRFML4d-NMoYvnbpmw@mail.gmail.com>
2014-03-19 18:37     ` Simon Glass
2014-02-28  6:27 JYOTI DUBEY
2014-02-12 10:55 JYOTI DUBEY
2014-02-13  0:56 ` TigerLiu at viatech.com.cn
2014-02-15 19:30   ` 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=52FC83D2.80106@denx.de \
    --to=hs@denx.de \
    --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