freenode
13m agov10 of 69-patch series adds HDMI 2.0 to DW HDMI QP TX (Rockchip) plus DRM connector init refactor and tests. 15m agoNew PEP 842 proposes __export__ to control module symbol visibility, prompting discussion on conventions vs __all__ and performance. 30m agoPatch series proposes kfuncs allowing BPF LSM programs to apply pre-created Landlock rulesets at exec time. 36m agoPatch series fixes BPF verifier bug in zero-extension tracking across pruning points using static liveness analysis. 36m agoFedora shadow-stack plans may force -fcf-protection into manylinux build flags to avoid future dlopen breaks for binary wheels. 39m agoPatch switches page reporting workqueue to freezable variant to prevent UAF on virtio device teardown during suspend. 39m ago31-patch series fixes pahole BTF multi-dimensional array encoding bug plus leaks, dead code, and replaces system() with posix_spawnp. 52m agoMTK users report JIT times scaling poorly with observed density in large repeated-structure models; discuss graph compilers and hints for repeated substructures. 2h agoDRM series adds HDMI 2.0 scrambling for Rockchip DW HDMI QP 3h agoGNOME cuts vuln embargo to 30 days, stops AI-ban forwards 4h agoThe IESG should reject solo ML-KEM for TLS and keep the hybrid safety net 5h ago8250 serial console conversion to NBCON queued again after earlier revert
AnalysisInternet & Protocols4h ago

The IESG should reject solo ML-KEM for TLS and keep the hybrid safety net

An IETF-wide last call asks the steering group to publish pure ML-KEM key agreement for TLS 1.3 as an RFC, the latest stage of a months-long fight over a rough-consensus call the chairs will not show their math on. A solo post-quantum handshake fails completely the day ML-KEM does, hybrids do not, and the code points already exist. The IESG should reject it. Comments close 13 August.