CVE information now contains separate version range for mainline and
stable nginx version.
Problem is that mainline version range includes stable verion fix and
since cve-check marks CVE as applicable if one of ranges contains
current recipe version, it's reported as vulnerable.
* Affected 1.29.2 < 1.31.6 (semver) < matches 1.30.5, so false positive
* Affected 1.30.4 < 1.30.5 (semver) < correct fix version, but overridden
Add also a note to remove these explicit entries when new minor stable
version is available which does not fall into the mainline version range
(for all 3 currently explicitly handled CVEs).
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Now that oe-core moved to OpenSSL 4.0, the engine API is gone.
As a result uboot-mkimage's -N/--engine no longer work:
Failed to sign 'signature-1' signature node in 'conf-imx6dl-riotboard.dtb' conf node
uboot-mkimage Can't add hashes to FIT blob: -1
Error: Bad parameters for FIT image type
Usage: uboot-mkimage [-T type] -l image
-l ==> list image header information
-T ==> parse image file as 'type'
-q ==> quiet
A previous patch documented how provider-based PKCS#11 signing works.
Now make an engine option in FITIMAGE_MKIMAGE_EXTRA_ARGS a fatal error. It
has no effect anymore, so a recipe still setting it has not been
migrated; failing with a clear message beats mkimage's generic error
messages above.
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Now that oe-core moved to OpenSSL 4.0, the engine API is gone.
As a result uboot-mkimage's -N/--engine no longer work:
Failed to sign 'signature-1' signature node in 'conf-imx6dl-riotboard.dtb' conf node
uboot-mkimage Can't add hashes to FIT blob: -1
Error: Bad parameters for FIT image type
Usage: uboot-mkimage [-T type] -l image
-l ==> list image header information
-T ==> parse image file as 'type'
-q ==> quiet
Document the provider-based setup instead: signing_create_uri_pem() wraps
the role's PKCS#11 URI in a PEM file that OpenSSL loads like a key file and
resolves through the PKCS#11 provider configured by signing_prepare().
mkimage looks for a key in
${FITIMAGE_SIGN_KEYDIR}/${FITIMAGE_SIGN_KEYNAME}.key, so store it there.
This way the existing mkimage invocations do not need to be touched.
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The pypi class has slightly changed the semantics of the PYPI_PACKAGE
variable[1], now PYPI_PACKAGE is the normalised package name and the new
variable PYPI_PACKAGE_SDIST is used when the source tarball doesn't match.
Update recipes as appropriate: this is mostly deleting now-redundant
assignments but some assignments are still needed where packages are not
uploaded using the modern standards.
[1] oe-core 98049bf86b6 ("classes/pypi: change PYPI_PACKAGE to be normalised")
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
libfuse 3.18.3 replaced its pytest based tests with shell test cases
driven by test/run-tests.py, so the pytest based run-ptest collected no
tests at all.
- Run test/run-tests.py from run-ptest and turn its result lines into
ptest PASS/FAIL/SKIP lines. Use a run directory under the canonical
/tmp, since some test filesystems mirror the real tree and cannot
follow the /var/tmp symlink.
- Install fuse_config.h, which the runner reads from the build tree.
- Replace the pytest dependencies with the python3 modules the runner
uses, and add coreutils and util-linux-losetup for dd status=none and
losetup --show, which busybox does not support.
- Do not print strerror(0) in test_syscalls, musl's "No error
information" is flagged as suspicious output by the runner.
All 87 tests now run on qemux86-64 musl: 80 pass, 7 skip.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The test added in 1.13 runs the sender through ${srcdir}/../libtool,
which only exists in the build tree. In ptest the sender cannot start
and the test fails with exit status 127. Skip it like the other valgrind
tests already do when libtool is not available.
AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Now that ibus-native doesn't exist, there's no need to have split .bb
and .inc files.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
We were building ibus-native for the unicode-parser tool that is needed
at build time. However, ibus can correctly build that (and other tools)
in cross-compiled environments since 1.5.29[1], so there's no need to
have a native recipe anymore.
[1] ibus 18f0d9f5 ("configure: Fix cross compiling")
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 0.22.0:
- BREAKING: Setting gc=False on a struct type that has a weakref
slot, whether from weakref=True or from a base class, now raises
ValueError. On CPython 3.12 and later the weakref slot is stored
in a pre-header in front of the instance, so releasing an instance
of a gc=False type with that slot corrupted memory, in most builds
crashing the interpreter outright. The combination worked on 3.10
and 3.11, and the restriction applies there as well, so that the
same class definition behaves the same way on every supported
version.
- Add frozendict support on Python 3.15+.
- Support passing a callable as decimal_format to
msgspec.json.Encoder and msgspec.msgpack.Encoder for custom
Decimal encoding.
- Support Literal[True] and Literal[False] types.
- Publish CPython 3.15 wheels, including freethreaded builds.
- Publish Linux riscv64 wheels.
- Support the PyEmscripten (Pyodide) platform.
- Fix handling of PEP 695 type parameter syntax (class Foo[T]) and
of types.GenericAlias instances in type annotations.
- Fix NameError when creating a Struct with an unquoted forward
reference on Python 3.14.
- Fix a crash on incorrect typing.ClassVar annotations (#1097).
- Fix an AttributeError when converting to a Struct type defined in
a namespace without a __name__ (#1072).
- Fix overriding an inherited field alias back to the field's own
name.
- Raise ValidationError instead of SystemError when convert receives
an out-of-range int for a float target (#1162).
- Report raw rather than the misleading any as the expected type
when a non-Raw value is given for a Raw field in convert, and
therefore in yaml.decode and toml.decode.
- Fix an empty expected-type name in validation errors for a
required Raw field in a TypedDict, or a Raw field with a
default_factory on a dataclass or an attrs class.
- Correct the error messages for out-of-range Meta length bounds.
- Fix a reference leak when decoding msgpack Ext payloads.
- Fix backing type declaration of Ext.code.
- Fix a reference leak in msgspec.to_builtins, and therefore in
yaml.encode, for array_like=True structs.
- Fix reference leaks in typenode_collect_literal,
Meta.__rich_repr__, ms_decode_bigint, and Encoder.__init__.
- Fix msgspec.inspect.type_info and msgspec.json.schema crashing
on mixed-type Literals such as Literal[1, None].
- Place null last in the anyOf generated for optional unions in
JSON schemas.
- Fix minItems in the JSON schema for array_like=True structs whose
fields are all optional.
- Use [] or "" rather than a Python set or bytearray object as the
JSON schema default for Struct fields with a set or bytearray
default_factory.
- Preserve JSON Schema metadata and string constraints in
propertyNames for annotated dictionary key types.
- Fix msgspec.json.encode raising TypeError for a dict keyed by a
plain enum.Enum with str values.
- Fix missing GC traversal and clearing of some module state
members.
- Ensure an exception is always set on allocation failures.
- Fix compilation warnings on Python 3.15.
- Report the leading argument of the encode and decode functions
and methods as positional-only in inspect.signature and the
rendered docs, matching runtime behavior.
- Add overloads to the Meta type stub, so type checkers reject
mixing gt with ge or lt with le.
- Many type stub improvements and fixes.
- Document the differences between msgspec.structs.asdict/astuple
and msgspec.to_builtins.
- Document that omit_defaults ignores fields with a custom
default_factory.
- Fix the msgspec.json.decode docstring to say dec_hook should
raise NotImplementedError for unsupported types, not TypeError.
- msgspec moved to the msgspec GitHub organization.
- documentation now lives at msgspec.dev.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 5.1.6:
- Use Datagram icmp_id and seq_id to match time exceeded messages
- docs: add Russian translation and fix typo in README
- docs: add Russian translation and cross-links
- Also use datagram icmp_id and seq to match destination
unreachable messages
License-Update: Remains MIT
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The do_compile() step removes flags from the kernel Makefile
before building the selftests.
On older kernels (pre-5.12), -mrecord-mcount is guarded by a
cc-option probe:
ifeq ($(call cc-option-yn,-mrecord-mcount),y)
CC_FLAGS_FTRACE += -mrecord-mcount
endif
Previously, the sed expression matched mrecord-mcount regardless
of its context in the line. This removed both the flag assignment
and the ifeq guard, leaving an orphaned endif and causing the
selftest build to fail.
Anchor the expression on += so that the sed only removes flag
assignments, giving us more precise control over which Makefile
lines are deleted.
Apply the same adjustment to the -Wno-alloc-size-larger-than
expressions for consistency.
Signed-off-by: Leonid Iziumtsev <leonid.iziumtsev@est.tech>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
1.8.4:
* Add support of
- THALES PKI Transaction Pad
* fix some minor issues found by an AI tool
1.8.3:
* Add support of
- Broadcom Corp 58200 0x5884
- Broadcom Corp 58200 0x5885
- Broadcom Corp 58200 0x5886
- Broadcom Corp 58200 0x5887
- Circle CIR135 ICC
- DigiFlow LLP. KAZTOKEN
- HID Global Crescendo NFC Reader
- HID Global OMNIKEY Plug
- HID Global OMNIKEY SE Plug
- Neowave LinkeoC-PRO
- Swissbit iShield Key 2 Pro
* macOS: provide a sample script to build the driver with meson
* fix some minor issues found by an AI tool
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Notable user-visible changes:
- Attempting to set zero parallel streams is no longer allowed.
- Zerocopy and rx-copy are now allowed in the case of reverse
direction tests and the server (sending side) supports these
features but the client (receiving side) does not.
- The limit on GSO_MAX_DG_IN_BF was fixed to limit the number of segments
to the maximum allowed. This change unbreaks GSO for small message sizes.
Changelog:
https://github.com/esnet/iperf/releases/tag/3.22
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Peter Marko
Bastian Krause
Ross Burton
Khem Raj
Leon Anavi
Leonid Iziumtsev
Ankur Tyagi