<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/image-host.c, branch v2024.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/image-host.c?h=v2024.07</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/image-host.c?h=v2024.07'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2024-04-12T14:53:31Z</updated>
<entry>
<title>image-host: Fix error value paths and emit error messages to stderr.</title>
<updated>2024-04-12T14:53:31Z</updated>
<author>
<name>Hugo Cornelis</name>
<email>hugo.cornelis@essensium.com</email>
</author>
<published>2024-03-21T11:22:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=55a7d60f8f10b1c3c5a8e29571c065d61f5dd12f'/>
<id>urn:sha1:55a7d60f8f10b1c3c5a8e29571c065d61f5dd12f</id>
<content type='text'>
A recent refactoring in image-host.c messed up the return values of
the function that reads the encryptiong keys.  This patch fixes this
and also makes sure that error output goes to stderr instead of to
stdout.

Signed-off-by: Hugo Cornelis &lt;hugo.cornelis@essensium.com&gt;
</content>
</entry>
<entry>
<title>image-host: refactor and protect for very long filenames</title>
<updated>2024-01-18T22:50:27Z</updated>
<author>
<name>Hugo Cornelis</name>
<email>hugo.cornelis@essensium.com</email>
</author>
<published>2024-01-08T14:24:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bc01d9ff93f350a35c51ddb75f81c2a6f663b1c1'/>
<id>urn:sha1:bc01d9ff93f350a35c51ddb75f81c2a6f663b1c1</id>
<content type='text'>
This patch adds a function fit_image_read_key_iv_data that checks the
return value of snprintf and allows to generate a sensible error
message when generating binary images using filenames that are too
long for the OS to handle.

This is especially relevant for automated builds such as Buildroot and
Yocto builds.

Signed-off-by: Hugo Cornelis &lt;hugo.cornelis@essensium.com&gt;
</content>
</entry>
<entry>
<title>tools: fix build without LIBCRYPTO support</title>
<updated>2024-01-12T03:09:11Z</updated>
<author>
<name>Paul-Erwan Rio</name>
<email>paulerwan.rio@gmail.com</email>
</author>
<published>2023-12-21T07:26:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=03e598263e3878b6f5d58f5525577903edadc644'/>
<id>urn:sha1:03e598263e3878b6f5d58f5525577903edadc644</id>
<content type='text'>
Commit cb9faa6f98ae ("tools: Use a single target-independent config to
enable OpenSSL") introduced a target-independent configuration to build
crypto features in host tools.

But since commit 2c21256b27d7 ("hash: Use Kconfig to enable hashing in
host tools and SPL") the build without OpenSSL is broken, due to FIT
signature/encryption features. Add missing conditional compilation
tokens to fix this.

Signed-off-by: Paul-Erwan Rio &lt;paulerwan.rio@gmail.com&gt;
Tested-by: Alexander Dahl &lt;ada@thorsis.com&gt;
Cc: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>tools: image-host: print error messages to stderr</title>
<updated>2023-08-30T15:47:43Z</updated>
<author>
<name>Oleksandr Suvorov</name>
<email>oleksandr.suvorov@foundries.io</email>
</author>
<published>2023-08-17T15:36:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8d8851e8fd52fdfbafd1dcb5faa66f20f9588d97'/>
<id>urn:sha1:8d8851e8fd52fdfbafd1dcb5faa66f20f9588d97</id>
<content type='text'>
The make by default cuts off the stdout output from external tools,
so all error messages from the image-host are not shown in a make
output. Besides that, it is a common approach to use stderr stream
for error messages.
Use stderr for all error messages in image-host.

Signed-off-by: Oleksandr Suvorov &lt;oleksandr.suvorov@foundries.io&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Add a few more messages for FIT failures</title>
<updated>2023-01-18T18:49:13Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-12-21T23:08:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=90cfae2ade358018bd46f84dba435eabccd4f8f6'/>
<id>urn:sha1:90cfae2ade358018bd46f84dba435eabccd4f8f6</id>
<content type='text'>
Add messages to make it clearer which part of the FIT creation is failing.
This can happen when an invalid 'algo' property is provided in the .its
file.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: fit: Fix signing of configs with external data</title>
<updated>2022-10-26T15:36:06Z</updated>
<author>
<name>Sean Anderson</name>
<email>sean.anderson@seco.com</email>
</author>
<published>2022-10-20T19:41:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0abe3323f5062032f8deb71cdc0635b124855d16'/>
<id>urn:sha1:0abe3323f5062032f8deb71cdc0635b124855d16</id>
<content type='text'>
Just like we exclude data-size, data-position, and data-offset from
fit_config_check_sig, we must exclude them while signing as well.

While we're at it, use the FIT_DATA_* defines for fit_config_check_sig
as welll.

Fixes: 8edecd3110e ("fit: Fix verification of images with external data")
Fixes: c522949a29d ("rsa: sig: fix config signature check for fit with padding")
Signed-off-by: Sean Anderson &lt;sean.anderson@seco.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>image-pre-load: Move macros/definitions to image.h</title>
<updated>2022-10-11T19:40:48Z</updated>
<author>
<name>Steven Lawrance</name>
<email>steven.lawrance@softathome.com</email>
</author>
<published>2022-09-14T18:57:27Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7c5eeb8309a19c662efe6d7695c256975f6da0d4'/>
<id>urn:sha1:7c5eeb8309a19c662efe6d7695c256975f6da0d4</id>
<content type='text'>
Putting these definitions in a header will allow signatures to be
validated independently of bootm.

Signed-off-by: Steven Lawrance &lt;steven.lawrance@softathome.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>tools: mkimage: Avoid ENODATA in host tools</title>
<updated>2022-05-05T23:37:11Z</updated>
<author>
<name>Mark Kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2022-04-26T17:24:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=616571804a01f032bc43fa4fdeb42f00cb90513c'/>
<id>urn:sha1:616571804a01f032bc43fa4fdeb42f00cb90513c</id>
<content type='text'>
ENODATA isn't part of POSIX.  Use EINVAL instead.

Signed-off-by: Mark Kettenis &lt;kettenis@openbsd.org&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>mkimage: add public key for image pre-load stage</title>
<updated>2022-03-31T18:12:01Z</updated>
<author>
<name>Philippe Reynes</name>
<email>philippe.reynes@softathome.com</email>
</author>
<published>2022-03-28T20:57:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6e052d1cbafbedbfba73070da483111f2ae68e5a'/>
<id>urn:sha1:6e052d1cbafbedbfba73070da483111f2ae68e5a</id>
<content type='text'>
This commit enhances mkimage to update the node
/image/pre-load/sig with the public key.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Philippe Reynes &lt;philippe.reynes@softathome.com&gt;
</content>
</entry>
<entry>
<title>tools: mkimage: Show where signatures/keys are written</title>
<updated>2022-01-26T15:50:44Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-11-12T19:28:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2d2384bbaff0ab84c868b553c74048a5f6acc9e3'/>
<id>urn:sha1:2d2384bbaff0ab84c868b553c74048a5f6acc9e3</id>
<content type='text'>
At present mkimage displays the node information but it is not clear what
signing action was taken. Add a message that shows it. For now it only
supports showing a single signing action, since that is the common case.

Sample:

   Signature written to 'sha1-basic/test.fit',
       node '/configurations/conf-1/signature'
   Public key written to 'sha1-basic/sandbox-u-boot.dtb',
       node '/signature/key-dev'

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
