agent: the report of release 0.175.1
gates / gates (push) Successful in 47s

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-15 12:11:20 +01:00
1 parent 5798b4bc2b
commit 3411592b80
1 file changed
+16 -29
+16 -29
View File
@@ -1,31 +1,18 @@
# REPORT — v0.174.0 released, vouched and delivered to the three test boxes (2026-11-14, attended)
# REPORT — agent 0.175.1 (2026-11-15)
**Plain words first.** A box now removes its old kernels by itself, and it reloads its security profiles after it
starts on another kernel. Version 0.174.0 is released and runs on Tester 1, demo-hp and the N100. The operator vouched
it at 15:21 CET. The N100's time service runs again; the product repaired it, with no hand step.
Released and vouched in the attended run of 2026-11-15. The full report is felhom.eu `REPORT-release-2b-3-2026-11-15.md`.
The full report of the run is in `felhom.eu`: `REPORT-release-2a-2026-11-14.md`.
## What a reader must know
1. **The clean-up runs on a box with the root-owned ring-0 mark only.** Tester 1 has no mark, so the program answers
„not run" there. For the proof the operator allowed the mark on Tester 1 for some minutes; it is back as before.
2. **The real removal on Tester 1 was started by hand**, with the agent's own command line. The night leg cannot be
started by day: it follows only the night's own backup (R-899). So „the step by the agent at night" is **not proven
yet**; the N100's and demo-hp's night of 2026-11-15 is the proof.
3. **The profile refresh was spiked first** on demo-hp (felhom.eu `audits/profile-refresh-spike-2026-11-14/`). Three
things it found are built in: a stale copy is told by the cached file changing, not by the kernel's hash; one
profile never compiles the same twice; a refresh hides other kernel audit lines for a few seconds.
4. **A clock step makes the controller read a new boot** (felhom.eu R-1395, a controller row): on the N100 it
recreated three apps once.
| | |
|---|---|
| Version | 0.174.0, sha256 `6efbb97809135483bc446d71d1321f9e2f7fc3268fe9b20e7fe742a2eb13db92`, bundle `7d87d0584dee79eee766f01c27b9e89273d39c89a14b0725a6e5564a55b3ec5f`, Go 1.27.4 |
| Code commit, CI | `cc63dd5`, run id 2641 success |
| Tests | wrapper 191 (42 new), agent `internal/osupdate` green; 30 mutations, each seen red (felhom.eu `audits/release-2a-2026-11-14/A`, `B`) |
| Tester 1 | 3 kernels → 2, 1.12 GB gained, 8.5 s; second run: nothing; one restart, same kernel, healthy, clean stop |
| demo-hp | nothing to remove; refusals P1, P2, P3 by dry run |
| The N100 | time service repaired (offset −32.55 s → +0.18 s); tonight it removes 6 of 8 kernels |
| Vouch | the operator, 2026-11-14 15:21:45 CET; `pinned.day0_agent` = 0.174.0 |
| Not proven | the step at night by the agent; a fell-back box and a self-revert into the kept kernel on a box; K1 on a box |
- **What:** trust in Proxmox by a copy of the box's own root CA, with the move from a pinned certificate; the report
carries the clock at sending; a refused signed job, a guest-power give-up, the kernel clean-up detail and the
profile refresh reach the hub; a boot key that a clock step cannot move; a cut write of `agent.json` is repaired at
start; root files older than the agent are not a trust problem on a pinned box.
- **Versions:** 0.175.1 — binary sha256 `38b1e2350de90a7940c16f8cd2a21d83fcd535410d1017a7df0fee14f0904612`, bundle
`07ebf86362ed9d44776416bd5c2c4b6b629e44d34595a8120fd8fc3f4d9277ff`, from `88d5d56`, CI run 2678; vouched 2026-11-15
11:07:35 CET; the day-0 pin is set. 0.175.0 (from `db01ae0`) was released the same morning, reached Tester 1 only,
and is NOT vouched: it raised one false trust alarm between the agent update and the root-files update.
- **Proven on boxes:** Tester 1, demo-hp and the N100 moved (a working call with the copy first, the fingerprint
cleared last); two forced new Proxmox certificates on demo-hp with no restart and no alarm; a wrong CA copy repaired
at start; a fresh install starts with the copy and no fingerprint; the clock alarm at the hub.
- **Tests only:** the repair after a real power cut; the refused-job and give-up messages.
- **Open:** a fully blind box sends no report (felhom.eu R-1396 gap 2); one Proxmox call answered 500 at day-0 with no
ERROR line (R-1397).