From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mkimage: Build signing only if board has CONFIG_FIT_SIGNATURE
Date: Thu, 27 Jun 2013 17:47:12 -0400 [thread overview]
Message-ID: <20130627214712.GC28078@bill-the-cat> (raw)
In-Reply-To: <20130627225519.14a314b1@lilith>
On Thu, Jun 27, 2013 at 10:55:19PM +0200, Albert ARIBAUD wrote:
> Hi Simon,
>
> On Thu, 27 Jun 2013 10:43:18 -0700, Simon Glass <sjg@chromium.org>
> wrote:
>
> > If CONFIG_FIT_SIGNATURE is not enabled, then mkimage will report a warning
> > that signing is not supported.
>
> Not sure I understand this scenario. Can you develop?
mkimage is stand-alone and for example, some distributions build and
ship a copy. If they build it without ssl stuff installed, their
distribution shipped copy will not be able to make signed images. I'll
make sure to spell things out in the release notes.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130627/80855f5f/attachment.pgp>
next prev parent reply other threads:[~2013-06-27 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:43 [U-Boot] [PATCH] mkimage: Build signing only if board has CONFIG_FIT_SIGNATURE Simon Glass
2013-06-27 20:55 ` Albert ARIBAUD
2013-06-27 21:47 ` Tom Rini [this message]
2013-06-28 6:48 ` Andreas Bießmann
2013-06-28 6:52 ` Simon Glass
2013-06-28 7:02 ` Andreas Bießmann
2013-06-28 7:11 ` Simon Glass
2013-06-28 8:21 ` Lubomir Popov
2013-06-28 7:00 ` [U-Boot] [PATCH] lib/rsa/rsa-sig.c: compile on OS X Andreas Bießmann
2013-06-30 13:08 ` Andreas Bießmann
2013-06-28 22:07 ` [U-Boot] [PATCH] mkimage: Build signing only if board has CONFIG_FIT_SIGNATURE Tom Rini
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=20130627214712.GC28078@bill-the-cat \
--to=trini@ti.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