OpenSSH 10.6 Introduces Post‑Quantum Signature Algorithm and Deprecates Experimental Keys
What Happened — The OpenSSH project released version 10.6, adding the hybrid post‑quantum signature algorithm ssh‑mldsa44‑ed25519 and disabling several legacy behaviours (compression dictionary, unsafe usernames, lingering GSSAPI credentials). Experimental keys that used the earlier post‑quantum support must be regenerated or removed.
Why It Matters for Trust & Control Assurance
- Demonstrates the need for continuous cryptographic‑algorithm governance – a control area that ensures only approved, vetted algorithms are in production.
- Highlights the importance of change‑management evidence – documenting updates, key regeneration, and configuration hardening as part of a defensible audit trail.
- Aligns with Verisq’s Control‑Mapping capability, which helps organisations map these software‑level changes to a single control objective that satisfies multiple frameworks (e.g., NIST CSF 2.0, ISO 27001).
Who Is Affected – Cloud‑infrastructure operators, SaaS providers, enterprise IT teams, and any organization that relies on OpenSSH for secure remote access.
Recommended Actions
- Upgrade all OpenSSH deployments to 10.6 without delay.
- Identify and replace any keys generated with the experimental post‑quantum algorithm.
- Update cryptographic policy to reflect the newly supported algorithm and deprecate the experimental one.
- Record the upgrade, key regeneration, and policy change in your control‑evidence repository.
Technical Notes – The release disables the LZ77 compression coder to mitigate a cross‑channel leakage attack, rejects command‑line usernames containing “$” or “\” to prevent shell injection, stores GSSAPI credentials only after successful authentication, and tightens SFTP path validation. No CVE identifiers were assigned; the changes address multiple previously reported bugs, many discovered with AI assistance. Source: Help Net Security