Skip to content

27 Oct 2026 · 0.15.0

AriCodeOS 0.15: the failure-pattern review

A week of public vulnerability news (OpenSSH, PHP, Node, Java’s TLS, rustls’ certificate checks) read for the methods behind each flaw rather than the language, and every place AriCodeOS made the same kind of mistake fixed: 47 findings, sixteen incidents and seven architecture decisions. Each fix reproduced before it was changed where that was possible, each branch audited independently, and the whole suite passed with 1 and 4 CPUs.

What changed

  • Authority closed on every path: the file service refuses a request whose session is gone and sshd keeps its host key in a directory of its own (ADR 0050); every graphical program gets a compositor session that alone owns its windows (ADR 0052), and applications can no longer ask for the raw keyboard (ADR 0053)
  • Devices checked, not trusted: the addresses a PCI device reports are checked against its BARs and the kernel’s own memory before anything is mapped (ADR 0051); virtio drivers keep their own queue bookkeeping, and a device loses access to a buffer its driver gave back (incident 0039)
  • Error paths that clean up: a process that fails to start frees all its memory (incident 0041), a partial IOMMU mapping is rolled back, and the supervisor no longer relaunches a service it gave up on (incident 0038)
  • Storage and parsers bounded: GPT tables read as a stream whatever size they declare, AriFS refuses to keep working on a half-applied commit (incident 0032), and WASM fuel counts work, imports included (ADR 0055)
  • Network and cryptography: TCP connections stuck closing are released, DHCP and DNS identifiers are random, the SSH server requires strict key exchange and signs in constant time, and the TLS seed never falls back to zeros (incidents 0035, 0036)
  • Distrusted keys (ADR 0054): certificate keys refused anywhere in a chain, starting with the eight eMudhra intermediates whose private keys were compromised this month
  • Fair diagnostics: one process can no longer push every other event out of the kernel’s event ring (incident 0040)
  • Pages backed with zeros on first touch, and a defined behaviour when memory runs out (ADR 0049)
  • Verified: the full suite, 197 scenarios with 1 and 4 CPUs, and development build 12 on the reference laptop, with network, USB keyboard and storage, SSH with an unchanged host key and HTTPS to GitHub and Google