From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: am33xx: security: adds auth support for encrypted images
Date: Fri, 29 Sep 2017 16:26:13 -0400 [thread overview]
Message-ID: <20170929202613.GR3112@bill-the-cat> (raw)
In-Reply-To: <20170920193736.30632-1-afd@ti.com>
On Wed, Sep 20, 2017 at 02:37:36PM -0500, Andrew F. Davis wrote:
> From: Madan Srinivas <madans@ti.com>
>
> This patch adds support for authentication of both plain
> text and encrypted binaries. A new SECDEV package is needed
> to enable encryption of binaries by default for AM3x.
>
> The ROM authentication API detects encrypted images at
> runtime and automatically decrypts the image if the
> signature verification passes.
>
> Addition of encryption on AM3x results in a change in the
> image format. On AM4x, AM5x and, on AM3x devices signing
> clear test images, the signature is appended to the end of the
> binary.
>
> On AM3x, when the SECDEV package is used to create signed
> and encrypted images, the signature is added as a header
> to the start of the binary. So the binary size calculation
> has been updated to reflect this change.
>
> The signing tools and encrypted image format for AM3x
> cannot be changed to behave like AM4x and AM5x to
> maintain backward compatibility with older Sitara
> M-Shield releases.
>
> Signed-off-by: Madan Srinivas <madans@ti.com>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170929/9739878f/attachment.sig>
prev parent reply other threads:[~2017-09-29 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 19:37 [U-Boot] [PATCH] arm: am33xx: security: adds auth support for encrypted images Andrew F. Davis
2017-09-29 20:26 ` Tom Rini [this message]
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=20170929202613.GR3112@bill-the-cat \
--to=trini@konsulko.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