summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-crypto
Commit message (Collapse)AuthorAgeFilesLines
* botan: upgrade 2.19.2 -> 2.19.3Chen Pei2022-12-201-1/+1
| | | | | | | | | | | | Version 2.19.3, 2022-11-16 CVE-2022-43705: A malicious OCSP responder could forge OCSP responses due to a failure to validate that an embedded certificate was issued by the end-entity issuing certificate authority. Signed-off-by: Chen Pei <cp0613@linux.alibaba.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit 2392dc79254a223da260c4b3b639d738e81b06a5) Signed-off-by: Armin Kuster <akuster808@gmail.com>
* libmcrypt: Suppress implicit-int warnings as errorsKhem Raj2022-09-051-0/+2
| | | | | | This is needed for clang-15+ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: Add support for building without SSH tokensPeter Kjellerstedt2022-06-301-2/+10
| | | | | | | | | Cryptsetup SSH tokens is the only feature that has a dependency on libssh. Add a packageconfig to control this dependency. Change-Id: Iac4f91e099ad2e3a79aab183734108f8bfbff57f Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* botan: upgrade 2.19.1 -> 2.19.2Wang Mingyu2022-06-061-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libtomcrypt: add recipeSamuli Piippo2022-05-311-0/+21
| | | | | | | | | | LibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines. Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: upgrade 1.28.0 -> 1.29.0wangmy2022-05-091-1/+1
| | | | | | | | | | | 2020-04-21 - Version 1.29.0 build: do not fail if slot evnets are disabled, thanks to Fabrice Fontaine. core: do not assume standard objects supported by provider. openssl: set back key into EVP for openssl-3 to work, thanks to apollo13. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: Add luks2 configure options defaultsAlejandro Enedino Hernandez Samaniego2022-05-041-0/+12
| | | | | | | | | | | | | | Cryptsetup allows for certain luks2 related defaults to be set for libcryptsetup, these include the default PBKDF algorithm, memory limit for Argon2, parallel threads and iteration time. Set default variables defined to the same values currently coming from cryptsetup upstream, making this change transparent for the user but allow these values to be customized. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: fix PVOleksandr Kravchuk2022-04-131-0/+0
| | | | | Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: Upgrade to 1.4.0Khem Raj2022-04-132-84/+4
| | | | | | | Drop upstreamed patch Disable new warnings seen with gcc 12 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fsverity-utils: Define LIBDIRKhem Raj2022-03-211-1/+1
| | | | | | | This helps make it platform independent since some platforms e.g. ppc64 uses lib64 for system libpaths Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes: Update LICENSE variable to use SPDX license identifiersKhem Raj2022-03-043-3/+3
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fsverity-utils: upgrade 1.4 -> 1.5Wang Mingyu2022-02-161-1/+1
| | | | | | | | | | | | | Changelog: ========= * Made the 'fsverity sign' command and the 'libfsverity_sign_digest()' function support PKCS#11 tokens. * Avoided a compiler error when building with musl libc. * Avoided compiler warnings when building with OpenSSL 3.0. * Improved documentation and test scripts. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: set precise BSD licenseRoss Burton2022-02-031-1/+1
| | | | | | | This package is BSD-3-Clause. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: update homepageRoss Burton2022-02-031-1/+1
| | | | | | | www.opensc-project.org expired, so point at the GitHub project page. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* botan: upgrade 2.18.2 -> 2.19.1wangmy2022-01-251-2/+2
| | | | | | | | | | | | License-Update: year updated to 2022. Changelog: ========= Fix a compilation problem affecting macOS XCode (GH #2880) Fix a build problem preventing amalgamation builds in 2.19.0 (GH #2879) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.4.2 -> 2.4.3wangmy2022-01-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelog: ========= Stable security bug-fix release that fixes CVE-2021-4122. All users of cryptsetup 2.4.x must upgrade to this version. Changes since version 2.4.2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Fix possible attacks against data confidentiality through LUKS2 online reencryption extension crash recovery (CVE-2021-4122). An attacker can modify on-disk metadata to simulate decryption in progress with crashed (unfinished) reencryption step and persistently decrypt part of the LUKS device. This attack requires repeated physical access to the LUKS device but no knowledge of user passphrases. The decryption step is performed after a valid user activates the device with a correct passphrase and modified metadata. There are no visible warnings for the user that such recovery happened (except using the luksDump command). The attack can also be reversed afterward (simulating crashed encryption from a plaintext) with possible modification of revealed plaintext. The size of possible decrypted data depends on configured LUKS2 header size (metadata size is configurable for LUKS2). With the default parameters (16 MiB LUKS2 header) and only one allocated keyslot (512 bit key for AES-XTS), simulated decryption with checksum resilience SHA1 (20 bytes checksum for 4096-byte blocks), the maximal decrypted size can be over 3GiB. The attack is not applicable to LUKS1 format, but the attacker can update metadata in place to LUKS2 format as an additional step. For such a converted LUKS2 header, the keyslot area is limited to decrypted size (with SHA1 checksums) over 300 MiB. The issue is present in all cryptsetup releases since 2.2.0. Versions 1.x, 2.0.x, and 2.1.x are not affected, as these do not contain LUKS2 reencryption extension. The problem was caused by reusing a mechanism designed for actual reencryption operation without reassessing the security impact for new encryption and decryption operations. While the reencryption requires calculating and verifying both key digests, no digest was needed to initiate decryption recovery if the destination is plaintext (no encryption key). Also, some metadata (like encryption cipher) is not protected, and an attacker could change it. Note that LUKS2 protects visible metadata only when a random change occurs. It does not protect against intentional modification but such modification must not cause a violation of data confidentiality. The fix introduces additional digest protection of reencryption metadata. The digest is calculated from known keys and critical reencryption metadata. Now an attacker cannot create correct metadata digest without knowledge of a passphrase for used keyslots. For more details, see LUKS2 On-Disk Format Specification version 1.1.0. The former reencryption operation (without the additional digest) is no longer supported (reencryption with the digest is not backward compatible). You need to finish in-progress reencryption before updating to new packages. The alternative approach is to perform a repair command from the updated package to recalculate reencryption digest and fix metadata. The reencryption repair operation always require a user passphrase. WARNING: Devices with older reencryption in progress can be no longer activated without performing the action mentioned above. Encryption in progress can be detected by running the luksDump command (output includes reencrypt keyslot with reencryption parameters). Also, during the active reencryption, no keyslot operations are available (change of passphrases, etc.). The issue was found by Milan Broz as cryptsetup maintainer. Other changes ~~~~~~~~~~~~~ * Add configure option --disable-luks2-reencryption to completely disable LUKS2 reencryption code. When used, the libcryptsetup library can read metadata with reencryption code, but all reencryption API calls and cryptsetup reencrypt commands are disabled. Devices with online reencryption in progress cannot be activated. This option can cause some incompatibilities. Please use with care. * Improve internal metadata validation code for reencryption metadata. * Add updated documentation for LUKS2 On-Disk Format Specification version 1.1.0 (with reencryption extension description and updated metadata description). See docs/on-disk-format-luks2.pdf or online version in https://gitlab.com/cryptsetup/LUKS2-docs repository. * Fix support for bitlk (BitLocker compatible) startup key with new metadata entry introduced in Windows 11. * Fix space restriction for LUKS2 reencryption with data shift. The code required more space than was needed. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: upgrade 1.27 -> 1.28wangmy2022-01-053-93/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 0001-build-openssl-remove-RSA_SSLV23_PADDING-constant-usa.patch 0001-nss-use-nss-pkcs11-h.patch removed since they're included in 1.28. Changelog: ========= * build: openssl: remove RSA_SSLV23_PADDING constant usage due to openssl-3 compatibility. * build: nss: use nss pkcs11.h * build: windows: checksum in PE * build: windows: support openssl-1.1.1 * mbed: require >=mbedtls-2, mbed dropped polarssl compatibility, * certificate: add methods accept full mechanism * core: load provider library as private. * core: add pkcs11h_getProperty, pkcs11h_setProperty to support adding properties without breaking API. * core: add pkcs11h_initializeProvider, pkcs11h_registerProvider, pkcs11h_setProviderProperty, pkcs11h_setProviderPropertyByName to support adding properties without breaking API * core: add initialization arguments property * core: add PKCS11H_PROVIDER_PROPERTY_PROVIDER_DESTRUCT_HOOK. * session: respect login required token flag. * certificate: respect always authenticate flag. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: Fix build with nss >= 3.73.1Khem Raj2021-12-252-0/+62
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: Fix build with muslKhem Raj2021-12-212-1/+84
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
* libkcapi: update to 1.3.1Oleksandr Kravchuk2021-12-152-41/+3
| | | | | | | | | Dropped upstreamed patch. License-Update: copyright years updated. Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.4.1 -> 2.4.2wangmy2021-11-221-1/+1
| | | | | Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: set precise BSD licenseRoss Burton2021-11-181-1/+1
| | | | | | | "BSD" is ambiguous, use the precise license BSD-3-Clause. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: remove DEPENDS on target libtoolRoss Burton2021-11-181-2/+0
| | | | | | | There is no need to build depend on the target libtool. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes: Update SRC_URI branch and protocolsRichard Purdie2021-11-033-3/+3
| | | | | | | | | This patch updates SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls as generated by the conversion script in OE-Core. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* botan: upgrade 2.18.1 -> 2.18.2wangmy2021-11-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Version 2.18.2, 2021-10-25 Avoid using short exponents when encrypting in ElGamal, as some PGP implementations generate keys with parameters that are weak when short exponents are used (GH #2794) Fix a low risk OAEP decryption side channel (GH #2797) Work around a miscompilation of SHA-3 caused by a bug in Clang 12 and XCode 13. (GH #2826) Remove support in OpenSSL provider for algorithms which are disabled by default in OpenSSL 3.0 (GH #2823, #2814) Add CI based on GitHub actions to replace Travis CI (GH #2632) Fix the online OCSP test, as the certificate involved had expired. (GH #2799) Fix some test failures induced by the expiration of the trust root "DST Root CA X3" (GH #2820) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.3.6 -> 2.4.1wangmy2021-10-251-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cryptsetup 2.4.1 Release Notes ============================== Stable bug-fix release with minor extensions. All users of cryptsetup 2.4.0 should upgrade to this version. Changes since version 2.4.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Fix compilation for libc implementations without dlvsym(). Some alternative libc implementations (like musl) do not provide versioned symbols dlvsym function. Code now fallbacks to dlsym operation for dynamic LUKS2 token load. It is up to maintainers to ensure that LUKS2 token plugins are compiled for the supported version. * Fix compilation and tests on systems with non-standard libraries (standalone argp library, external gettext library, BusyBox implementations of standard tools). * Try to workaround some issues on systems without udev support. NOTE: non-udev systems cannot provide all functionality for kernel device-mapper, and some operations can fail. * Fixes for OpenSSL3 crypto backend (including FIPS mode). Because cryptsetup still requires some hash functions implemented in OpenSSL3 legacy provider, crypto backend now uses its library context and tries to load both default and legacy OpenSSL3 providers. If FIPS mode is detected, no library context is used, and it is up to the OpenSSL system-wide policy to load proper providers. NOTE: We still use some deprecated API in the OpenSSL3 backend, and there are some known problems in OpenSSL 3.0.0. * Print error message when assigning a token to an inactive keyslot. * Fix offset bug in LUKS2 encryption code if --offset option was used. * Do not allow LUKS2 decryption for devices with data offset. Such devices cannot be used after decryption. * Fix LUKS1 cryptsetup repair command for some specific problems. Repair code can now fix wrongly used initialization vector specification in ECB mode (that is insecure anyway!) and repair the upper-case hash specification in the LUKS1 header. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: backport a openssl 3.x patchAlexander Kanavin2021-10-142-1/+30
| | | | | Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: Add runtime dependency on lvm2-udevrules for udevKristian Klausen2021-09-071-1/+1
| | | | | | | Without the udevrules cryptsetup luksOpen will be hanging with "Udev cookie 0xd4de0f6 (semid 5) waiting for zero". Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: allow an option to build nativelySinan Kaya2021-08-251-0/+2
| | | | | Signed-off-by: Sinan Kaya <okaya@kernel.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: add a hash only packageconfigSinan Kaya2021-08-251-0/+1
| | | | | Signed-off-by: Sinan Kaya <okaya@kernel.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Convert to new override syntaxMartin Jansa2021-08-034-16/+16
| | | | | | | | | | This is the result of automated script (0.9.1) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* cryptsetup: Only recommend kernel modules when building for targetPeter Kjellerstedt2021-06-281-12/+13
| | | | | | | | | | | | | | | | | | | | Otherwise cryptsetup-native depends on the target kernel and thus the target compiler, as can be seen by: $ bitbake -g cryptsetup-native $ grep 'cryptsetup.*linux-yocto' task-depends.dot "cryptsetup-native.do_build" -> "linux-yocto.do_deploy" "cryptsetup-native.do_build" -> "linux-yocto.do_package_write_rpm" "cryptsetup-native.do_populate_sysroot" -> "linux-yocto.do_populate_sysroot" $ grep 'linux-yocto.*gcc-cross' task-depends.dot "linux-yocto.do_kernel_configme" -> "gcc-cross-x86_64.do_populate_sysroot" "linux-yocto.do_prepare_recipe_sysroot" -> "gcc-cross-x86_64.do_populate_sysroot" This also moves the runtime dependencies to near the end of the recipe, which is more customary. Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fsverity-utils: upgrade 1.3 -> 1.4zangrc2021-06-181-1/+1
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.3.5 -> 2.3.6zangrc2021-06-101-2/+2
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* botan: upgrade 2.14.0 -> 2.18.1Andreas Müller2021-05-241-2/+1
| | | | | Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: DEPEND on renamed util-linux-libuuidKhem Raj2021-03-261-1/+1
| | | | | | | OE-core recipe is called util-linux-libuuid now Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Luca Boccassi <luca.boccassi@microsoft.com>
* cryptsetup: upgrade 2.3.4 -> 2.3.5zhengruoqin2021-03-191-2/+2
| | | | | Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: depend on new util-linux-uuid to break cycleLuca Boccassi2021-03-121-1/+1
| | | | | | | | | | | | | | | | | The util-linux recipe in Poky has been split, and libuuid is separate now: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d42487bf52310d095178e480b7ddec2666471009 This allows to build util-linux with cryptsetup, for native dm-verity support. The main cryptsetup build needs libuuid and not the full util-linux, so switch the build-dependency over, thus allowing users to enable the cryptsetup util-linux's PACKAGECONFIG. The libblkid dependency is handled individually by the crypsetup's PACKAGECONFIG option. Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libmcrypt: Run autoreconf steps manuallyKhem Raj2021-02-081-0/+11
| | | | | | This helps in re-running the configure generation with autotools 2.70+ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fsverity: fix MinGW buildLuca Boccassi2021-01-201-1/+4
| | | | | | | Upstream supports building a binary with MinGW but not a shared library, so remove the configure option for MinGW targets. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fsverity: update to 1.3Luca Boccassi2021-01-201-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pkcs11-helper: upgrade 1.26 -> 1.27zangrc2020-11-271-2/+2
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: Fix build on riscv32Khem Raj2020-11-162-1/+39
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* botan: Mark incompatible with riscv32Khem Raj2020-11-151-0/+2
| | | | | | CPU is not supported _yet_ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: upgrade 1.2.0 -> 1.2.1Zang Ruochen2020-11-021-1/+1
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Add recipe for fsverity-utilsLuca Boccassi2020-10-211-0/+28
| | | | | | | | | | | Library and command-line tool to manage the fs-verity feature, introduced in Linux 5.4 and supported in ext4 and f2fs filesystems. https://www.kernel.org/doc/html/latest/filesystems/fsverity.html Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.3.3 -> 2.3.4Zang Ruochen2020-09-101-2/+2
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libkcapi: update to 1.2.0Oleksandr Kravchuk2020-07-283-120/+3
| | | | | | | | | | Removed patches were upstreamed. License checksum changed due to modified copyright years (see @8397f0f7c45264a). Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libmcrypt: set CLEANBROKENChangqing Li2020-06-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | reproduce steps: 1. bitbake libmcrypt 2. add bb.note('hello') in do_fetch of base.bbclass 3. bitbake libmcrypt do_configure failed: Making clean in doc make[1]: Entering directory 'build/tmp-glibc/work/cortexa72-wrs-linux/libmcrypt/2.5.8-r0/libmcrypt-2.5.8/doc' make[1]: *** No rule to make target 'clean'. Stop. make[1]: Leaving directory 'build/tmp-glibc/work/cortexa72-wrs-linux/libmcrypt/2.5.8-r0/libmcrypt-2.5.8/doc' Makefile:316: recipe for target 'clean-recursive' failed error occurred in autotools_preconfigure, since we have build one time in step1, we have CONFIGURESTAMPFILE, and also BB_TASKHASH changed after step2, in step3, after do_fetch, ${S} is renewed, but with main Makefile exist but no Makefile exist under sub folder, so above error occurred. set CLEANBROKEN to fix this error Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* cryptsetup: upgrade 2.3.2 -> 2.3.3Zang Ruochen2020-06-101-2/+2
| | | | | Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 10:20:36 +0000