Files
felhom.eu/documentation/audits
admin 418f3a2c20
gates / gates (push) Successful in 20s
chaos night round 8: the accident did not do what its name said
Round 8 (backup-app nextcloud + internet cut) passed on the product side:
26 containers throughout, LAN doors served the whole ten minutes, public
path restored unaided in <=43 s, no alarm fired and none should have.

The finding is against my own instrument. The hub report due at 22:38:43Z
fell inside the cut and SUCCEEDED, because hub.felhom.eu resolves to a LAN
address (192.168.0.192, measured from guest and host) and the injector
allowed the whole LAN. So rounds 7 and 8 never tested hub unreachability,
and the dropped-event behaviour is still unmeasured.

Two fixes, both to the harness, neither to the product:
  * inject.sh now blocks the hub address from the VM's side (the host tap
    rule). The hub itself is untouched - the fence is kept. It refuses to
    inject at all if it cannot resolve the hub.
  * run_round.sh no longer reads the front doors 3 s after an unblock. Every
    door reading now states its own timestamp and a second reading is taken
    60 s later. This was the sixth mistimed reading of the night.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-17 00:52:40 +02:00
..
@
2026-07-14 00:45:20 +02:00
@
2026-07-14 10:12:21 +02:00
@
2026-07-14 12:17:26 +02:00
@
2026-07-14 12:17:26 +02:00