Files
rust-discovery/docs/server-time-source-new-generation-probe.md
2026-11-15 12:14:12 +01:00

89 lines
5.6 KiB
Markdown

# One native source sample for the proven c9 generation
The user-approved Chrony generation change actually passed. Generation result
`d648daadc43de90cda977ce60615b8e47072b785aa9fbfaea37ef8b58be6c9d4`
and separate Root read receipt
`58970ef8e89af86b68fdbbf2cb5119210bcb37cec603feb23b4f6030b0b36623`
bind the new daemon and public pin. This is a non-quality bootstrap result.
No native source sample or signed time authority follows from it.
`deploy/server_time_source_new_generation_probe.py` defines one new create-only
subphase `/var/lib/rmm-time-source-bootstrap/c9a94f94-eecd-4c66-933d-c45c1a79c7a8/probe-native-source-v1`.
It executes only the original root:root 0500 AArch64 probe from the 5b build:
848,632 bytes, SHA256
`216b4d6a0f29ef47576f5ccc469954623141e55d7b43bd73175c1d956363bbbd`.
The named-client provider remains exactly source3fd. The fixed systemd-run
profile remains root:989 with empty supplementary groups, NoNewPrivileges,
CAP_SYS_PTRACE plus CAP_DAC_OVERRIDE, strict root filesystem protection,
AF_UNIX only, IPAddressDeny, private tmp/devices, the original syscall deny list,
3-second runtime limit and 10-second owned command watchdog. Only the unit/case
identity changes. There is one sample attempt and no automatic retry.
Two proofs deliberately remain separate:
- `QualifiedBuild` reads and holds the original preflight/stage/build records,
archive0da5, manifestbdf7, complete verified workspace and both original
root500 ELF artifacts. The build result is pinned to58eaf011. These records
describe the old generation historically. No old `pin.Original` constructor,
freshness check, monkeypatch, PID adoption or reset is used.
- `SharedGenerationProof(pin)` imports exactly the protected Root600 fac/ecb/d5
source bytes. It retains original FDs for all17 actual c9 records with their
exact Root read hashes and metadata; the other21 fixed record names must stay
absent. It checks the195-byte current public pin395f and complete metadata
against the result, after/CAS/new-pin records and old194-byte backup. Fresh
complete ecb process/cgroup/socket/runtime/boot observations must match the
new after record. Public configuration, typed D-Bus commands and actual
AppArmor/ACL namespace must equal d5's recorded after state.
The shared read-only API exports `CASE_ID`, `QUALITY_PHASE`,
`SharedGenerationProof(pin)`, `.operator`, `.operator_guard`, `.artifacts`,
`.source_sha`, `.manifest_sha`, `.expected`, `.public_pin_raw`,
`.public_pin_metadata`, `.target_directories`, and `.records` mapping Path to
original raw bytes/metadata. `.fresh()` returns the six actual new pin fields;
`.namespace_verify()` returns the checked namespace. `.close()` releases all
held FDs. Directory identities use dev/inode/UID/GID/mode and ACLs, permitting
incidental parent directory timestamps from later owned broker bootstrap files.
The shared proof never reads signer-key contents or assumes a broker must remain
absent. The one native-probe host action separately enforces no broker/time key.
Intent, before witness and a separate start intent precede the only execution.
The raw log and actual exit are preserved before sample validation. The positive
schema is exactly the previous ca89 sample schema: same boot UUID, exact known
fields, integer time domains, total error at most500ms, reference age at most1h,
kernel state0..4, and explicit false clock/signature authority. Before/after
witnesses must be identical. Result, raw log and both witnesses are hash-linked.
`quality_proof(expected_result_sha256)` validates that same format read-only and
returns the four held records for a broker adapter. A caller must already pin a
real independently reviewed positive result hash; None cannot open this gate.
`host-read` reads only the original fixed subphase and metadata. It runs no
preflight, service command, probe, time query or effect. A lost reply or partial
phase permits only that original read, never a new phase or replay. No command
changes clocks, Chrony service/configuration, public pin, capabilities, ACL/MAC,
signer keys, broker installation, RMM jobs or application runtime.
Status: source/local qualification only. Root must separately review, stage
`new_generation_probe.py` as Root600 under its content hash, then execute one
`host-probe` and a separate `host-read`. Native quality remains unproven until
those actual records pass; all old5b failed probe cases remain unchanged.
## Tatsächlich native Qualität auf dem permanenten Server bestanden
Originalfallc9/`probe-native-source-v1`: genau eine Ausführung des
unveränderten AArch64-Probes216b/848632Bytes nach unabhängigem Review.
Tatsächlicher Exit0 und striktes Sample validiert. Kernelstate0, konservativer
Gesamtfehler50.833923ms, tatsächliches gutes Quellensync43.596197206s alt;
keine Werte aus Pollzeit oder bloßem Heartbeat abgeleitet. Before/After-Zeugen
identisch e72ce5f6; Runtime, Boot, neue Pin-/Chrony-/Configbindung erhalten.
Rootreceipt `1aab3af930648aed260c4c66a1c3ff068656cae016fcc301f052880926f99c93`.
Separater ausschließlich lesender Originalrückabruf de6273d1 bestätigt Exit0,
Sample, identische Zeugen und Resultat-SHA256
`ab8a6511517c6e3c01db2351ccdc5c48c73f34112c9ac863d0ea64de46665933`;
Readreceipt `7005ef54759412cd0d95e558ceebbf524a55c04bf6641c8241161e0d5e81fbf3`.
Dieser neue erfolgreiche Beleg ersetzt keinen früheren Fehler und ist keine
Signatur oder Jobgenehmigung. Kein Signer/Key/Broker/HTTPendpoint oder
Windowsclock wurde durch die Probe aktiviert. Erst dieser konkrete aktuelle
Nachweis darf den getrennten geschützten Signerbootstrap ermöglichen. Jeder
spätere Brokerbeleg benötigt trotzdem seine eigene neue NativeTimeSource-Probe.