Debian Patches

Status for rauc/1.13-3+deb13u1

Patch Description Author Forwarded Bugs Origin Last update
src-signature-fix-compatibility-with-OpenSSL-3.5-for.patch [PATCH 2/2] src/signature: fix compatibility with OpenSSL 3.5 for purpose registration

OpenSSL 3.5 warns that there may be gaps, so we need to search. When our
minimum version is at least 3.5, we can switch this to
X509_PURPOSE_get_unused_id().		 Jan Luebbe <jlu@pengutronix.de> no https://github.com/rauc/rauc/pull/1697 2025-04-15
disable-network-tests.patch Disable tests that fail in debian build chroot Uwe Kleine-König <u.kleine-koenig@pengutronix.de> not-needed vendor, Debian 2023-10-10
install-wrapper-to-pkgdatadir.patch Install dbus wrapper script to /usr/share/rauc instead of /usr/libexec
According to the FHS /usr/libexec is for binaries only, so /usr/share/rauc
seems to be better suited for a shell script.		 Uwe Kleine-König <u.kleine-koenig@pengutronix.de> not-needed vendor, Debian 2023-10-10
0001-src-signature-protect-against-integer-overflows-with.patch src/signature: protect against integer overflows with BIO_new_mem_buf()

BIO_new_mem_buf()'s len argument is of type int, so it cannot support
lengths exceeding 2 GiB. Reject larger lengths and additionally check
that we have created the BIO correctly.

These are only internal checks, GError handling will be added in a later
commit.		 Jan Luebbe <jlu@pengutronix.de> no 2026-03-25
0002-src-signature-reject-plain-bundles-with-payload-exce.patch src/signature: reject plain bundles with payload exceeding 2 GiB
Due to BIO_new_mem_buf() only supporting buffers of up to 2 GiB, we
cannot sign or verify bundles with a payload larger than that.

This fixes an integer overflow which would lead to calling
BIO_new_mem_buf() with a negative len, which will cause it to use
strlen() to to determine the buffer size automatically. As a result,
the buffer is truncated at the first '\0' byte in the SquashFS header.
The first 4 bytes are a fixed magic number ("hsqs"), and since a '\0'
byte appears within the inode count field at bytes 5-8 in most SquashFS
images, the resulting signature will only cover this part of the
SquashFS header.

As we sign or verify the payload directly via OpenSSL only for the
'plain' format, the 'verity' and 'crypt' formats are not affected.

Fix this by checking the content size before calling cms_sign_file() or
cms_verify_bytes(), which call BIO_new_mem_buf() via bytes_as_bio().		 Jan Luebbe <jlu@pengutronix.de> no 2026-03-25
src-context-fix-library-reinitialization.patch [PATCH 1/2] src/context: fix library reinitialization
In the test suite, we sometimes recreate the context, which caused
multiple initialization of the network and signature dependencies. With
OpenSSL 3.5, this leads to purpose ID collisions, as we try to add the
same purpose multiple times.

Avoid this by remembering if the have initialized our dependencies
already.		 Jan Luebbe <jlu@pengutronix.de> no https://github.com/rauc/rauc/pull/1697 2025-04-15

All known versions for source package 'rauc'

Links