Skip to content

27 Oct 2026 · 0.16.0

AriCodeOS 0.16: the review, closed

It finishes the failure-pattern review that 0.15 started, including the parts of the certificate finding and the thirteen informational findings 0.15 had left as stated. Eight incidents and five architecture decisions, each audited until the audit came back clean; two audits found serious problems in a first version, and both were fixed before merging.

What changed

  • Certificate names: the common name is never read as a host name (ADR 0058), an IPv4 host matches the certificate’s IP entries, and no wildcard stands on a public suffix such as *.co.uk (ADR 0062)
  • Cryptography (incident 0044): AES without lookup tables, constant-time comparisons protected from the compiler, Ed25519 refusing small-order keys (1160 of 12 544 forgeries were accepted; now none) and secrets wiped after use
  • Updates fail closed (ADR 0060): a damaged boot record is rebuilt from the slot that booted, and a damaged downgrade floor refuses stable releases until the owner consents
  • SSH (incident 0046): an authorized_keys line with options is refused with its line number, and every authentication attempt counts against the limit
  • Kernel (incident 0047, ADR 0057): a closed handle never becomes valid again, the DMA quota is refunded when an allocation fails, and typed input meant for a crashed program is discarded
  • PCI (incident 0050, ADR 0061): a dead driver’s interrupt line can no longer silence its replacement, and MSI-X is used only where the device’s table is still in place
  • Tests fixed, not retried: a port-lease race (incident 0049) and an IOMMU fault count read too early with 4 CPUs (incident 0051)
  • Verified: the full suite, 202 scenarios with 1 and 4 CPUs, and the reference laptop

0.16.1 (2 Nov 2026) is the bridge to 0.17: it gives 0.16.0 only the new updater, which streams images into the UPDATE partition (ADR 0064), because the 6.8 MB image of 0.17 does not fit the old updater’s 6 MiB.