<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/image-host.c, branch v2025.04</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=v2025.04</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/image-host.c?h=v2025.04'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2025-02-18T18:30:32Z</updated>
<entry>
<title>tools: use cryptographically safe RNG</title>
<updated>2025-02-18T18:30:32Z</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>heinrich.schuchardt@canonical.com</email>
</author>
<published>2025-02-11T13:55:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=50e8089c1de107137c7a30fd5691ebd449f42e2d'/>
<id>urn:sha1:50e8089c1de107137c7a30fd5691ebd449f42e2d</id>
<content type='text'>
The PRNG implementing the random() function only has 2^31 states and
therefore is unsafe to use for cryptography. Use arc4random() instead.

Fixes: cc34f04efd63 ("tools: image-host.c: use random instead of rand")
Addresses-Coverity-ID: 312953 Calling risky function
Signed-off-by: Heinrich Schuchardt &lt;heinrich.schuchardt@canonical.com&gt;
</content>
</entry>
<entry>
<title>Merge patch series "upl: Prerequite patches for updated spec"</title>
<updated>2025-01-22T23:08:47Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2025-01-22T22:08:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a3b71cc6f5cc74d4edc5808790a3d2999ea3f7fe'/>
<id>urn:sha1:a3b71cc6f5cc74d4edc5808790a3d2999ea3f7fe</id>
<content type='text'>
Simon Glass &lt;sjg@chromium.org&gt; says:

The current UPL spec[1] has been tidied up and improved over the last
year, since U-Boot's original UPL support was written.

This series includes some prerequisite patches needed for the real UPL
patches. It is split from [2]

[1] https://github.com/UniversalPayload/spec/tree/3f1450d
[2] https://patchwork.ozlabs.org/project/uboot/list/?series=438574&amp;state=*

Link: https://lore.kernel.org/r/20250111000029.245022-1-sjg@chromium.org
</content>
</entry>
<entry>
<title>boot: Rename fit_image_get_data()</title>
<updated>2025-01-22T21:58:04Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2025-01-11T00:00:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=dc39ce8d90770a9abf9d464f7d29624361173c78'/>
<id>urn:sha1:dc39ce8d90770a9abf9d464f7d29624361173c78</id>
<content type='text'>
This function can only be used with FITs that use embedded data. Rename
it so this is clear.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Acked-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
</content>
</entry>
<entry>
<title>aes: Allow to store randomly generated IV in the FIT</title>
<updated>2024-12-19T15:10:34Z</updated>
<author>
<name>Paul HENRYS</name>
<email>paul.henrys_ext@softathome.com</email>
</author>
<published>2024-11-25T17:47:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=79d7b11102e31f3b92afff1c94dd9fe1a8b9a9e4'/>
<id>urn:sha1:79d7b11102e31f3b92afff1c94dd9fe1a8b9a9e4</id>
<content type='text'>
When the initialisation vector is randomly generated, its value shall be
stored in the FIT together with the encrypted data. The changes allow to
store the IV in the FIT also in the case where the key is not stored in
the DTB but retrieved somewhere else at runtime.

Signed-off-by: Paul HENRYS &lt;paul.henrys_ext@softathome.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>image-host: fix 'unknown error' error message</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Alexander Kochetkov</name>
<email>al.kochet@gmail.com</email>
</author>
<published>2024-09-16T08:24:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9e81f13dbb41843abb25e6c4b20961f092630f13'/>
<id>urn:sha1:9e81f13dbb41843abb25e6c4b20961f092630f13</id>
<content type='text'>
Fix error message like this:
Can't add verification data for node 'fdt-1' (&lt;unknown error&gt;)

We get unknown error because we decode error as fdt error
but actually it is system error.

Signed-off-by: Alexander Kochetkov &lt;al.kochet@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Allow 'auto-conf' signing of scripts</title>
<updated>2024-07-05T19:57:01Z</updated>
<author>
<name>Alexander Dahl</name>
<email>ada@thorsis.com</email>
</author>
<published>2024-06-20T14:20:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6074f6e85783f582e8524778fff170ff05b35a91'/>
<id>urn:sha1:6074f6e85783f582e8524778fff170ff05b35a91</id>
<content type='text'>
U-Boot configured for verified boot with the "required" option set to
"conf" also checks scripts put in FIT images for a valid signature, and
refuses to source and run such a script if the signature for the
configuration is bad or missing.  Such a script could not be packaged
before, because mkimage failed like this:

    % tools/mkimage -T script -C none -d tmp/my.scr -f auto-conf -k tmp -g dev -o sha256,rsa4096 my.uimg
    Failed to find any images for configuration 'conf-1/signature'
    tools/mkimage Can't add hashes to FIT blob: -1
    Error: Bad parameters for FIT image type

This is especially unfortunate if LEGACY_IMAGE_FORMAT is disabled as
recommended.

Listing the script configuration in a "sign-images" subnode instead,
would have added even more complexity to the already complex auto fit
generation code.

Signed-off-by: Alexander Dahl &lt;ada@thorsis.com&gt;
</content>
</entry>
<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>
</feed>
