AlmaLinux releases OS 10.3 and 9.9 with post-quantum security and Podman 6
AlmaLinux 10.3 and 9.9 introduce significant updates to development toolsets, container orchestration via Podman 6, and post-quantum cryptographic support.
Summary
The AlmaLinux OS Foundation has announced the general availability of AlmaLinux 10.3, codenamed "Mauve Lion," and AlmaLinux 9.9, codenamed "Chartreuse Bobcat." The 10.3 release serves as a major version bump, featuring kernel 6.12 and a significant overhaul of the container subsystem through the transition to Podman 6.
Both releases prioritize modern development environments and enhanced security. Key updates include new toolsets for GCC, LLVM, Rust, and Go, alongside the integration of post-quantum key exchange mechanisms in security components like libreswan and opencryptoki. Additionally, AlmaLinux 10.3 restores ModSecurity and the OWASP Core Rule Set to the distribution.
Technical breakdown of AlmaLinux 10.3 and 9.9
- Container Subsystem: AlmaLinux 10.3 moves to Podman 6, which replaces CNI networking with Netavark, swaps the BoltDB backend for SQLite, and replaces slirp4netns with pasta for rootless networking.
- Post-Quantum Cryptography: Security updates include libreswan 5.4 with ML-KEM key exchange, audit 4.2 supporting post-quantum TLS for remote logging, and opencryptoki 3.27 with ML-DSA and ML-KEM support.
- Development Toolsets: Both versions introduce GCC Toolset 16 (defaulting to C++20), LLVM Toolset 22, Rust 1.97, and Go 1.27, providing updated compilers and runtimes for enterprise workloads.
- Kernel and Hardware: AlmaLinux 10.3 utilizes kernel 6.12.0-264.16.1.el10_3, while 9.9 uses kernel 5.14.0-741.22.1.el9_9; both support x86_64, ARM64, IBM PowerPC, and IBM Z architectures.
- Security Policy Management: The fapolicyd 2.0 update enables parallel decision-making and atomic transactions for policy and trust database updates.
Why it matters
The transition to Podman 6 and the removal of cgroups v1 and iptables in favor of nftables requires careful planning for container administrators. Furthermore, the inclusion of post-quantum cryptographic standards prepares enterprise Linux environments for future-proofed secure communications.
What to do
- If you run container workloads on AlmaLinux 10.3, check that you don't rely on CNI networking, BoltDB, slirp4netns, cgroups v1, or iptables before upgrading.
- If you use ModSecurity rules from AlmaLinux 9, review them before putting 10.3 in front of production traffic because CRS 4 reorganized the rule set.
- If your systems combine group records from multiple sources, re-enable group merging after upgrading with: authselect enable-feature with-group-merging
Original reference: almalinux.org →