20 Oct 2026 · 0.12.0
AriCodeOS 0.12: a hardened network and file service
The release audit of 0.11, resolved through the failure protocol: ten incidents closed and five architecture decisions, each fix on its own branch with regression tests, audited twice and verified on the reference laptop.
What changed
- USB storage: both drivers reject a status wrapper that did not move exactly 13 bytes, and the xHCI driver no longer reports a short transfer as a success (incidents 0007, 0010)
- Updates: a failed file request is never taken for an absent file (0008), and every network phase of the updater, TLS included, stays within its deadline (0009, ADR 0033)
- TCP sequence numbers and ephemeral ports derived from a per-boot secret, as in RFC 6528 and RFC 6056 (0014, ADR 0034)
- SYN floods capped per listening socket and answered with a stateless reset; the TCP table by state in diag (0013, ADR 0035)
- Per-client sessions in the network and file services: when a client dies, its sockets, descriptors and half-finished replacements are reclaimed, and no client can touch another’s (0011, 0016, ADR 0036, 0037)
- Network refusals named in the shell and recorded as fault events (0012), and a bounded number of frames per receive round
- The scheduler self-test is correct on SMP (0015), and the Docker images work on ARM hosts
- Verified on the laptop with version 8 from a production-signed index: storage, network, HTTPS and no fault event at boot