Why we cannot wait for better post-quantum signature algorithms – ML-DSA now

Heavy AI news day — GPT-5.6, Grok 4.5, Muse Spark all landed within 24h. We picked the items that actually help you operate things.

// SECURITY FOCUS

Why we cannot wait for better post-quantum signature algorithms – ML-DSA now

NIST has nine new post-quantum signature candidates in the pipeline, but Cloudflare’s analysis concludes none are ready to deploy at scale today – ML-DSA (FIPS 204) is the only standardized option with real implementation maturity. If you’re planning post-quantum rollout timelines around those candidates, this changes the calculus: you’re likely deploying ML-DSA first whether you want to or not, and your TLS termination and signing infrastructure needs to account for ML-DSA’s larger signature sizes now.

What to do: Audit your TLS and code-signing stack for ML-DSA readiness this quarter; don’t hold the roadmap for NIST candidate finalization.

  1. EPIPE on write might mean you’re doing it wrong — Rachel by the Bay · Jul 10
    Rachel digs into Apache + php-fpm pipe blockage – the kind of subtle Unix I/O problem where EPIPE is a symptom pointing at a broken assumption about backpressure, not the root cause. Required reading if you’re running fastcgi stacks and seeing intermittent hangs under load.
  2. Rust 1.97.0 released: new symbol mangling by default, Cargo deny-warnings, linker output restored — Rust Blog · Jul 9
    Rust 1.97.0 ships with three notable changes: the v0 symbol mangling scheme – introduced in 1.59 and on nightly since November 2025 – is now the default on stable, with the legacy Itanium-based scheme restricted to nightly and slated for removal. Cargo gets a first-class warnings control via CARGO_BUILD_WARNINGS, accepting allow, warn (default), or deny; using it doesn’t bust the build cache, so you can temporarily silence warnings mid-refactor without a full rebuild. Linker output is no longer suppressed on successful links – it surfaces as a linker_messages warning lint, which is intentionally excluded from the standard warnings group since linker output varies by platform. The stabilized API batch adds integer bit-isolation helpers (isolate_highest_one, isolate_lowest_one, highest_one, lowest_one, bit_width) for both primitive integers and NonZero variants.
  3. Graviton5 CPU benchmarks: 30% geomean improvement over Graviton4 — Phoronix · Jul 9
    Phoronix benchmarked AWS Graviton5 (M9g) against Graviton4 (M8g) at the 16-vCPU / 64 GB 4xlarge size on Ubuntu 26.04 with Linux 7.0, finding a ~30% geomean improvement across the test suite – roughly matching AWS’s own marketing claims of 25-35% depending on workload type. Graviton5 moves from Neoverse-V2 to Neoverse-V3 (Armv9.2-A) cores, bumps the clock from 2.8 GHz to 3.3 GHz, scales to 192 cores, and upgrades memory from DDR5-5600 to DDR5-8800. The on-demand price premium is about 9% (from $0.718/hr to $0.783/hr in Ohio at 4xlarge), so the performance-per-dollar case is reasonably solid if the 30% figure holds for your actual workload. Graviton5 vs. AMD EPYC and Intel Xeon comparisons are coming in a follow-up, contingent on reader interest covering the cloud costs – worth watching before committing to a migration.
  4. Navigating the ingress-NGINX retirement — CNCF Blog · Jul 9
    The community-maintained ingress-nginx controller reached end of life in March 2026 – the Kubernetes Ingress API itself is not going away, just this specific controller. Teams now face two paths: swap in a drop-in replacement like Contour (keeping existing Ingress YAML but manually rewriting all nginx.ingress.kubernetes.io/* annotations), or migrate to Gateway API, which is the upstream-backed successor with role-oriented design, native traffic splitting, and cross-namespace routing. The CNCF post recommends Contour as a stopgap if engineering time is tight, since the Ingress API is feature-frozen and Gateway API requires a fuller refactor. The ingress2gateway tool can automate some translation work, and a parallel rollout – non-critical workloads first – reduces blast radius either way. If you’re already planning platform modernization, Gateway API is the long-term move; if you just need to stop the bleeding, swap the controller class and budget time to finish the job properly.
  5. Bun’s Rust rewrite with AI: 11 days, $165K in tokens, ~1 engineer-year of work — Pragmatic Engineer · Jul 9
    Bun’s creator Jarred Sumner used Anthropic’s Fable tool to rewrite Bun from Zig to Rust in 11 days, a migration Sumner estimates would have taken a small team 1-2 years by hand – at a token cost of $165K. The key caveat: Bun has extensive test coverage, which is what made an AI-assisted rewrite viable rather than reckless. The article also covers the broader coding-LLM competitive landscape (GPT-5.6 Sol, Grok 4.5 via Cursor, Meta’s Muse), plus a recurring hiring problem where North Korean developers are using AI filters to pass remote interviews at Western companies. If you’re weighing AI-assisted migration for a large codebase, the Bun case is the clearest real-world data point yet – but the test suite is the prerequisite, not the AI.

// In other news

ai

  • The new GPT-5.6 family: Luna, Terra, Sol (Simon Willison) · Jul 9 — GPT-5.6 ships in three sizes – Luna, Terra, Sol – with Sol being the largest; Simon Willison’s breakdown covers the practical capability and pricing differences worth knowing before migrating workloads.
  • Anthropic found a hidden space where Claude puzzles over concepts (MIT Technology Review AI) · Jul 9 — Anthropic’s new interpretability technique maps an intermediate ‘concept space’ inside Claude during inference – the clearest mechanistic view yet of how an LLM actually reasons before producing output.
  • llm 0.31.1 (Simon Willison) · Jul 9 — llm 0.31.1 patches a bug where OpenAI Chat Completion endpoints returned a broken token count – worth updating if you’re scripting against the CLI tool.
  • GPT-5.5 Bio Bug Bounty (OpenAI Blog) · Jul 9 — OpenAI is paying bounties for biosecurity vulnerabilities found in GPT-5.5, a rare public acknowledgment that frontier models need adversarial probing for dual-use biological risks.
  • llm-meta-ai 0.1 (Simon Willison) · Jul 9 — llm-meta-ai 0.1 lets you run prompts against Meta’s Muse Spark API via Simon Willison’s llm CLI – useful if you want to benchmark it locally without the web UI.

cloud

  • Safely run AI-generated code in Cloud Run sandboxes (Google Cloud Blog) · Jul 9 — Cloud Run Sandboxes hit public preview, offering gVisor-isolated execution for AI-generated or untrusted code without managing separate VM fleets – the key constraint is cold-start latency in sandbox mode.
  • Autopilot Clusters with GKE managed DRANET: GPUs and TPUs (Google Cloud Blog) · Jul 9 — GKE Autopilot now manages DRANET network allocation for GPU and TPU nodes, removing the manual topology-aware scheduling work that previously blocked teams from using Autopilot for ML training jobs.
  • Specification-driven composition for flexible data workflows (AWS Architecture) · Jul 9 — AWS Architecture blog details a spec-driven approach to data pipelines that reduces duplicated transformation logic as pipelines scale – worth a read if you’re hitting the ‘everything is a custom script’ wall.

culture

dev

iac

k8s

linux

obs

sec

web

  • WordPress 7.0.1 Maintenance Release (WordPress News) · Jul 9 — WordPress 7.0.1 fixes 31 bugs across core and the block editor – straightforward maintenance release, update your sites.
  • PHP version stats: July, 2026 (Stitcher.io) · Jul 9 — Stitcher’s biannual PHP version adoption numbers are out for July 2026 – the split between supported and EOL versions in production remains a useful reality check when targeting minimum PHP requirements.
  • Intercept: Middleware Guardrails for Laravel AI Agents (Laravel News) · Jul 8 — Intercept is a new Laravel package that adds middleware-style guardrails to AI agent pipelines – lets you inspect, block, or transform agent actions before they execute without coupling safety logic to business code.
  • CLAUDE.md is RAM, not disk (Freek Van der Herten) · Jul 9 — Freek Van der Herten argues CLAUDE.md should be treated as working memory rather than documentation – keep it under ~50 lines of active context, not a 300-line dumping ground of stale conventions.
  • AI Review for Laravel Upgrades (Laravel News) · Jul 8 — Laravel News covers using AI-assisted review to catch breaking changes during Laravel version upgrades – practical for teams who can’t dedicate a full sprint to upgrade regression testing.

Stay skeptical of geomeans. See you tomorrow.

Leave a comment