Repository navigation
AriCodeOS 0.15.0
AriCodeOS 0.15.0 (2026-10-27): the failure-pattern release. A week of public vulnerability news (OpenSSH, PHP, Node, Java's TLS, rustls' certificate checks) was read for the methods behind each flaw rather than the language, and every place AriCodeOS made the same kind of mistake was fixed: 47 findings, sixteen incidents (0028 to 0043) and seven ADRs (0049 to 0055). Each fix was reproduced before it was changed where a reproduction was possible, each branch had an independent audit, and the whole system passed its full test suite (197 scenarios, with 1 and with 4 CPUs) and ran on the reference laptop.
Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.15 · Review: docs/audits/2026-10-25-failure-patterns.md.
What is new
- 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, migrated on first boot with the fingerprint unchanged); every graphical program gets a compositor session that alone owns its windows (ADR 0052); 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 bound every device-reported offset; a driver's device loses access to a client's buffer once the driver gives it 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, init closes what a failed launch opened, and the supervisor no longer relaunches a service it gave up on (incident 0038).
- Storage and parsers bounded: GPT tables are read as a stream whatever size they declare, AriFS checks its layout and refuses to keep working on a half-applied commit (incident 0032), and the WASM interpreter's fuel now counts work, imports included (incident 0042, ADR 0055).
- Network and cryptography: TCP connections stuck closing are released, port 22 is reserved for sshd, DHCP and DNS identifiers are random, the SSH server requires strict key exchange and signs in constant time (incident 0035), certificates are checked against the release date when there is no trustworthy clock, and the TLS seed never falls back to zeros (incident 0036).
- Distrusted keys (ADR 0054): a list of certificate keys refused anywhere in a chain. It carries the eight eMudhra intermediates whose private keys were compromised this month (the same keys Go and rustls distrust). They chain to roots AriCodeOS does not embed, so no default chain reached them; the list also covers roots an owner adds.
- Fair diagnostics: one process can no longer push every other event out of the kernel's event ring (incident 0040).
- Found on the way: the screen console repainted the whole screen for every line, so slow output made some tests depend on where the kernel happened to land in memory (incident 0031); virtio-blk gave up on disk requests after 2 s, too short for a busy host disk (incident 0043, now 30 s).
Trying it
- USB stick (
aricodeos-0.15.0-usb.img.xz, attached;xz -dit first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; seedocs/hardware.md. Check it againstSHA256SUMS. Machines on 0.14.0 update from this page withupdateandupgrade. - Docker:
docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.15.0boots it in QEMU (quit with Ctrl-A X).
Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).
Known open items
System image downloads above 6 MiB and applications above 32 KiB (AriFS file size) need design decisions; agents outside the trusted base (ADR 0041) and the driver licence (ADR 0042) await the owner; the review left the common-name fallback and wildcards over public suffixes in X.509, and its informational findings, as stated; EHCI hubs and split transactions are only verifiable on hardware.