hub (unreleased): a box cannot mint operator events — only a queued job is told as refused, the give-up list is bounded (R-1383); docs for the clock-step fix and HSTS (R-1395, R-1050)
gates / gates (push) Successful in 2m3s

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-14 17:43:33 +01:00
1 parent 1886030782
commit 186f3fca58
11 files changed
+184 -14

No files matched your search

@@ -169,7 +169,9 @@ traefik's :443 and says so in `X-Forwarded-Proto: http` (measured), which traefi
The first link of the entrypoint chain `felhom-forwarded` (`felhom-https-only`) answers it with a 301 to the same https
URL, path and query kept, BEFORE any app sees the request — so a login page is never served, and a password never sent,
over http. A name with no app route is redirected by a priority-1 catch-all that matches only `X-Forwarded-Proto: http`.
HSTS: one day, no subdomains, no preload (a longer value is the operator's decision). **Where it is enforced:** on the box
HSTS: one day, no subdomains, no preload on every released controller. **[FACT — built, not released, 2026-11-14:
controller `main` sends one year (`31536000`), `09` §3 decision 249, R-1050; still no subdomains, no preload; the
release is built on or after 2026-11-15.]** **Where it is enforced:** on the box
(`dynamic/forwarded.yml`, rewritten on every health tick if it drifts), not at Cloudflare: the boxes' Cloudflare keys
cannot change zone settings (403, measured on every zone) — Cloudflare's „Always Use HTTPS" is the operator's optional
second layer. **How it is checked:** `scripts/https_only_check.py` lists every public name from the box's own traefik
@@ -659,6 +659,10 @@ Four cases, the four the ruling names. Each leaves an event row and mails the op
| A signed job a box took and refused, or whose run failed | the box's agent | the agent's clearing call (`DELETE …/jobs/<id>`) now carries `outcome` (done · rejected · failed · malformed), a `reason` from a closed list (`signedjobs.ReasonCodes`) and the op's name in its query; before, „ran” and „refused” looked the same | `signed_job_refused` (error), once per job. The two clock reasons name the box's clock | an agent older than release 3 says nothing, and nothing is raised. The box's own words never reach a mail (unknown reason → „other”) |
| The guest-power watchdog gave up | the box's agent | the host report's `guest_power_gave_up` list (vmid, since, attempts); the watchdog's record is memory | `guest_power_gave_up` (error), once per down period; `guest_power_ok` (info) when a later report shows that guest running | „gone from the list” alone never clears (an agent restart empties the list while the guest is still down) |
**What a box cannot do with these two channels:** a refused job is told only for a job that was in that box's own
queue, so a box cannot make operator mails by clearing job ids it invents; the give-up list is read only for guests
the same report lists (not running), 16 entries at most.
**Not proven on a box or a deployed hub:** all five. The tests use fakes for the mail service and the real gate
and verifier for the signed jobs (`audits/night-build-2026-11-14/B/`, 43 mutations seen red).