freenode
9m agoNixOS community debates whether to opt out of Hugging Face's code dataset over licensing, consent and LLM training use. 11m agoPatch series proposes kfuncs allowing BPF LSM programs to apply pre-created Landlock rulesets at exec time. 21m agoPahole patchset adds DWARF handling for Rust enums/variant_parts and dwz alternate files to improve BTF output. 23m agoProposal to add read_freeze to core::ptr using LLVM freeze for uninit memory reads without UB. 25m agoPatch series fixes BPF verifier zero-extension tracking bug across pruning by extending live register analysis to track upper/lower halves. 31m agoGNOME shortens embargo to 30 days and halts forwarding reports to AI-ban projects; thread debates policy effects. 32m agov10 of 69-patch series adds HDMI 2.0 to DW HDMI QP TX (Rockchip) plus DRM connector init refactor and tests. 33m agoDraft ERC discussion on verifiable, ordered memory-state transitions for autonomous agents, positioned to complete an existing agent-ERC stack. 80m agoDRM series adds HDMI 2.0 scrambling for Rockchip DW HDMI QP 2h agoGNOME cuts vuln embargo to 30 days, stops AI-ban forwards 3h agoThe IESG should reject solo ML-KEM for TLS and keep the hybrid safety net 4h ago8250 serial console conversion to NBCON queued again after earlier revert
AnalysisInternet & Protocols3h 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.