I have just submitted for testing
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4b1b8b8b25,
which updates llhttp from 8.1.1 to 9.1.3 in EPEL9. This is an
ABI-incompatible update, and the SONAME version changes. There are also
some minor API changes.
The only package in EPEL9 that uses llhttp is python-aiohttp, and the
update also compatibly updates it from 3.8.5 to its latest release, 3.9.1.
Together, these updates fix a number of security issues, including
CVE-2023-47627, CVE-2023-49081, and CVE-2023-49082.
A COPR impact check in
https://copr.fedorainfracloud.org/coprs/music/aiohttp-epel9/ indicates
there should be no impact on any dependent packages in EPEL9.
If you have software not packaged in EPEL9 that depends directly on
llhttp, you will need to rebuild it due to the ABI changes. It is
possible that source code changes may be required if (like
python-aiohttp) you use almost the entire API of llhttp, or if you have
very thorough tests that reveal small changes in llhttp’s behavior.
Straightforward uses of llhttp are likely to recompile without modification.
If you have software not packaged in EPEL9 that depends directly on
python-aiohttp, you should not need to do anything, but you might choose
to review the changelogs for releases 3.8.6, 3.9.0, and 3.9.1 here for
full details on the changes included in this update:
https://github.com/aio-libs/aiohttp/blob/v3.9.1/CHANGES.rst#391-2023-11-26
I have no plans to attempt a build of llhttp or any update of
python-aiohttp in EPEL8.
This is an incompatible update under the EPEL Incompatible Upgrades
Policy,
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/.
It was approved by the EPEL Steering Committee:
https://pagure.io/epel/issue/262.
After approval in the last EPEL meeting [1], I have submitted an incompatible upgrade of singularity-ce to testing for EPEL 7, 8 & 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cbd86d2020https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f299fbc570https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-05e20edbbf
These updates upgrade singularity-ce from v3.11.5 to v4.1.1.
The following incompatibilities should be noted by users:
1) Some functionality previously provided by the `singularity remote` command is split into new `singularity registry` and `singularity keyserver` commands.
2) The `singularity remote add` command now sets a newly added remote as the default (unless suppressed). Previously the user had to set the default remote manually.
3) The deprecated and unmaintained `—vm` flag to start singularity inside a Virtual Machine has been removed.
4) Bind mounts are now performed in the order in which they are specified. Previously, image based bind mounts were performed before others.
5) Current working directory on the host is now created in the container, restoring a behaviour from Singularity <3.6.0 unless suppressed.
6) If the current directory paths on the container and host contains symlinks to different locations, the current working directory is not mounted.
Changes 1,2,3 are expected to have minimal impact, and 4,5,6 are likely to be considered bug fixes by many users.
No changes are required to existing configuration files for this update.
A complete description of changes and additions between v3.11 and v4.1.1 is available in the upstream documentation at https://sylabs.io/docs/
In the absence of any issues, the updates will be pushed to stable after a one week testing period has passed, with a follow-up notification here.
Cheers,
David Trudgian
[1] https://pagure.io/epel/issue/265#comment-894790
The following Fedora EPEL 7 Security updates need testing:
Age URL
2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5ef433f7ed chromium-122.0.6261.69-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
resalloc-5.3-1.el7
scitokens-cpp-1.1.1-1.el7
Details about builds:
================================================================================
resalloc-5.3-1.el7 (FEDORA-EPEL-2024-ac2a36384a)
Resource allocator for expensive resources - client tooling
--------------------------------------------------------------------------------
Update Information:
New upstream release
https://github.com/praiskup/resalloc/releases/tag/v5.3https://github.com/praiskup/resalloc/releases/tag/v5.2https://github.com/praiskup/resalloc-aws/releases/tag/resalloc-aws-1.8-1
--------------------------------------------------------------------------------
ChangeLog:
* Wed Feb 28 2024 Pavel Raiskup <praiskup(a)redhat.com> - 5.3-1
- New upstream release https://github.com/praiskup/resalloc/releases/tag/v5.3
* Wed Feb 28 2024 Pavel Raiskup <praiskup(a)redhat.com> - 5.2-1
- New upstream release https://github.com/praiskup/resalloc/releases/tag/v5.2
* Fri Jan 26 2024 Fedora Release Engineering <releng(a)fedoraproject.org> - 5.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Mon Jan 22 2024 Fedora Release Engineering <releng(a)fedoraproject.org> - 5.1-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
--------------------------------------------------------------------------------
================================================================================
scitokens-cpp-1.1.1-1.el7 (FEDORA-EPEL-2024-f7e3e336c0)
C++ Implementation of the SciTokens Library
--------------------------------------------------------------------------------
Update Information:
Improve error handling around the sqlite3 library
Fix test failures and compiler warnings
--------------------------------------------------------------------------------
ChangeLog:
* Wed Feb 28 2024 Derek Weitzel <dweitzel(a)unl.edu> - 1.1.1-1
- Improve error handling around the sqlite3 library
- Fix test failures and compiler warnings
--------------------------------------------------------------------------------
The following Fedora EPEL 7 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c2135dc540 3proxy-0.9.4-2.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
chromium-122.0.6261.69-1.el7
Details about builds:
================================================================================
chromium-122.0.6261.69-1.el7 (FEDORA-EPEL-2024-5ef433f7ed)
A WebKit (Blink) powered web browser that Google doesn't want you to use
--------------------------------------------------------------------------------
Update Information:
Update to 122.0.6261.69
--------------------------------------------------------------------------------
ChangeLog:
* Fri Feb 23 2024 Than Ngo <than(a)redhat.com> - 122.0.6261.69-1
- update to 122.0.6261.69
- fix build error on el8
- bz#2265039, built with -fwrapv for improved memory safety
- bz#2265043, built with -ftrivial-auto-var-init=zero for improved security and preditability
* Wed Feb 21 2024 Than Ngo <than(a)redhat.com> - 122.0.6261.57-1
- update to 122.0.6261.57
* High CVE-2024-1669: Out of bounds memory access in Blink
* High CVE-2024-1670: Use after free in Mojo
* Medium CVE-2024-1671: Inappropriate implementation in Site Isolation
* Medium CVE-2024-1672: Inappropriate implementation in Content Security Policy
* Medium CVE-2024-1673: Use after free in Accessibility
* Medium CVE-2024-1674: Inappropriate implementation in Navigation
* Medium CVE-2024-1675: Insufficient policy enforcement in Download
* Low CVE-2024-1676: Inappropriate implementation in Navigation.
* Sun Feb 18 2024 Than Ngo <than(a)redhat.com> - 122.0.6261.39-1
- update to 122.0.6261.39
* Wed Feb 14 2024 Than Ngo <than(a)redhat.com> - 121.0.6167.184-1
- update to 121.0.6167.184
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #2265256 - CVE-2024-1669 CVE-2024-1670 CVE-2024-1671 CVE-2024-1672 CVE-2024-1673 CVE-2024-1674 CVE-2024-1675 CVE-2024-1676 chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2265256
--------------------------------------------------------------------------------