Stay Informed
This week, read about:
- SSH3, A Secure Version of SSH That Uses HTTP3.
- Linux Kernel 6.7 Release Is Loaded With Fixes and a New Filesystem.
- 6 Predictions for Linux and Open Source in 2024.
- The Top 5 Open Source News Stories of 2023.
- JDK 21 Security Enhancements.
- We Have the Latest Versions of OpenJDK Versions 8, 11, and 17 Now Available.
Key Security, Maintenance, and Features Releases
Security Based Updates
Updates to the OpenLogic CentOS Repository
*) OpenLogic’s Enterprise Linux Team has recently published the following updates:
- CVE-2023-4911
- CentOS 8
- glibc-2.28-164_ol002.el8
- CentOS 8
- CVE-2018-25032
- CentOS 8
- zlib-1.2.11-17_ol002.el8
- CentOS 8
- CVE-2022-2526
- CentOS 8
- systemd-239-51_ol001.el8_5.2
- CentOS 8
- CVE-2021-4157
- CentOS 8
- kernel-4.18.0-348.7.1_ol001.el8_5
- CentOS 8
- CentOS 6
- tzdata-2023c-1_ol001.el6
We recommend that you update your CentOS 6 systems to ensure proper timekeeping. As usual, please ensure that you test these updates before deploying to production. If you don't currently have CentOS repo access, please reach out to your Perforce/OpenLogic salesperson … you may already be entitled to access with your existing support contract!
Non-Security Based Updates
- Fix BZ 68378 - add mime type for mjs and others - aligning with httpd
- Align embedded MIME type mappings with BZ 68378 updates to web.xml
- Fix BZ 68348 - add support for the cookie attribute partitioned
- Improve French and Japanese translations.
RabbitMQ 3.12.12
Minimum Supported Erlang Version
- As of 3.12.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases.
- Users upgrading from 3.11.x (or older releases) on Erlang 25 to 3.12.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult
the v3.12.0 release notes first.
Changes Worth Mentioning
- Release notes can be found on GitHub at rabbitmq-server/release-notes.
Core Broker
Bug Fixes:
- Environments with a lot of quorum queues could experience a large Erlang process
build-up. The build-up was temporary but with a sufficiently large number of
quorum queues it could last until the next round of periodic operations,
making it permanent and depriving the node of CPU resources. - RabbitMQ core failed to propagate more authentication and authorization context, for example,
MQTT client ID in case of MQTT connections, to authN and authZ backends. This was not intentional. - Nodes now takes more precaution about persisting feature flag state
(specifically the effects of in-flight changes) during node shutdown.
Enhancements:
- Simplified some type specs.
Stream Plugin
- One returned error value did not match the RabbitMQ Stream Protocol specification.
MQTT Plugin
Bug Fixes:
- Recovering connections from QoS 0 consumers (subscribers) could fail if they were previously connected to a failed node.
CLI Tools
Bug Fixes:
- Since #10131 (shipped in 3.12.11, some CLI commands in certain scenarios could fail to accept input via standard output.
AWS Peer Discovery Plugin
Enhancements:
- Updated some type specs.
ActiveMQ 6.0.1
Bug Fixes:
[AMQ-9398] - Fix Jakarta EE 10 support via xml wiring for activmeq-ra
[AMQ-9399] - Clean-up OSGi headers for a couple modules
[AMQ-9405] - Supplied jetty.xml fails to load if ssl is enabled
[AMQ-9408] - Jolokia throws exception during Windows service startup
Improvement:
[AMQ-8133] - Consider adding IBM Z (s390x) into Apache ActiveMQ Jenkins CI
[AMQ-9328] - Update website cleaning/mentioning ActiveMQ 6.0.0 and update activemq component
Task:
[AMQ-9389] - Add JDK 22, arm and windows nodes to Jenkins builds
[AMQ-9401] - Minor doc update referencing javax instead of jakarta
Dependency Upgrade:
[AMQ-9402] - Upgrade to Shiro 1.13.0
[AMQ-9403] - Upgrade Jackson 2.16.0
[AMQ-9404] - Upgrade to Spring 6.0.14
[AMQ-9406] - Upgrade to Camel 4.2.0
[AMQ-9407] - Upgrade to log4j 2.22.0