Files
rust-discovery/docs/server-time-source-abstract-client.md
T

112 lines
6.8 KiB
Markdown

# Native Chrony client transport: abstract AF_UNIX
The native Linux source now binds one CSPRNG UUIDv4 name in the Linux abstract
AF_UNIX namespace. The leading NUL and exact sockaddr length select a kernel
name, without a trailing NUL or filesystem client socket. There is one bind
attempt. A collision fails the observation; the provider never adopts a name,
generates a replacement name after failure, or retries the request.
The root-protected `/run/rmm-time-source/clients` directory remains mandatory,
with its existing exact root/group/mode checks, held directory descriptor,
exclusive nonblocking flock and empty-directory precondition. Historical named
socket leftovers therefore still block the instance. The provider never deletes
or adopts them. Its own abstract address is checked with getsockname. Successful
observation explicitly consumes and closes the socket descriptor once before
returning quality; a close or verification error cannot return a qualified
sample. Drop closes remaining owned descriptors without an unlink or a close
retry. The source remains poisoned after a failed observation.
An abstract name grants no filesystem DAC authority. A different process could
reserve a guessed name first and deny bind, or cause denial of service. That
cannot create positive source quality: the kernel excludes a second bind, and
the source still connects only to the fixed protected Chrony pathname. The
pinned daemon PID, birth, image, UID/GID, held process identity, protected server
socket identity, exact single SCM_CREDENTIALS record, reply sequence and fixed
Tracking packet checks are unchanged. The monotonic/boottime/UTC brackets,
kernel-state, error, reference-age and signed-time contracts are unchanged.
The provider exposes no configurable endpoint, clock setter, signer, retry or
network transport.
The original named-client provider SHA
`3fd9c7a969a583abf97e29165135a8c1044db5c951ad8bd4dbfee3ee77e7ccdc`
and the original 5b build/failed GROUP, DAC and peer probe records remain
historical evidence. They are not overwritten or reclassified. Root's separate
abstract-connect-only diagnosis, receipt
`9bcdaa00b86346b85d73d5bb9d4e491ecd82ed108ca8ec8a0495f7ec19770d56`,
proved connect under the same two-capability profile without sending a
datagram. It did not produce a native quality sample. This transport change
requires its own published source build and native qualification before any
broker quality gate may open. It changes no AppArmor rule, ACL, capability,
Chrony service, public pin, signer key or RMM job.
Subsequent evidence blocks treating this implementation as a working Chrony
transport. Root's separate one-request diagnosis received no reply (receipt
`f82eef4fc7d8f7cab7971a835a68eef855f166c32cb2feaac191551188351881`).
The upstream Chrony 4.8/4.9 [socket.c](https://gitlab.com/chrony/chrony/-/raw/4.9/socket.c)
stores an AF_UNIX sender as `remote_addr.path`, then reconstructs the reply
address using `strlen` in `set_unix_sockaddr`. An abstract sender's leading NUL
therefore loses its random name. This source-level incompatibility explains the
observed connect/send success without a reply, subject to checking the installed
Chrony package's exact source. The local guards below prove kernel socket
semantics, not Chrony interoperability. No ARM quality acceptance or broker
installation may follow from these local results.
The local six-test qualification uses a frozen three-crate workspace, the held
original offline 70-package lock/recipe and current codec807 source. Two new
guards verify exact abstract sockaddr encoding and actual exclusive kernel bind
with release on close while an unrelated name stays reserved. The existing
clock-bracket and Tracking-parser guards remain; the obsolete filesystem-client
cleanup fixture is replaced by the retained server-socket protection guard.
Local tests do not call NativeTimeSource.open/sample, contact Chrony, or prove
ARM64 or real-server source quality. The existing ecb prepare flow can package
the newly published source tip after review; no handmade original manifest is
used.
Local qualification `945ec634-f787-4496-b019-28f03949f58f` actually passed six
default release lib tests (zero skipped/filtered), clippy with warnings denied,
rustfmt checking and the offline release operator-probe build. The release test
ELF is x86-64, 1,147,336 bytes, SHA256
`de9591c30f71d5a46d38cdb799051a22cb17617f2089bce2f12b9864c395462d`.
Its frozen receipt is
`082666f3d9c07ebda4e935d5a67d16d6a5d7b62963044a6c638f17ae0bc93d09`;
the provider source is
`8d13ef64f1b7ce0991f3d52a8a42d7b096e9020a57d4ca21a16409a4492e3a39`.
`deploy/time_source_abstract_linux_acceptance.py` provides only `prepare`, one
`execute`, and original-case `read`. It copies that exact frozen ELF and all
fourteen recipe/source inputs; it does not rebuild from a moving worktree. The
remote runner first requires the exact full six-test list, then runs the binary
without filters/skips. An intent precedes execution; local and remote case
creation reject repeats. Before/after witnesses bind the existing three RMM
service generations, protected controls, state-file identities and closed APT
service. Timeout cleanup targets only the held unreaped child group. It performs
no RMM job or native source query. After a lost reply, only the original `read`
is permitted. Local prepare of case
`b5e4e4cc-5bb7-441a-8c53-1fc2281e17e8` succeeded; target `execute` and `read`
remain unexecuted by this author and require Root's separate action.
## Actual Cloud-Linux fixture result; production candidate rejected
Root actually executed the six frozen guards in original case
`b5e4e4cc-5bb7-441a-8c53-1fc2281e17e8`:6PASS/0ignored/filtered,
receipt `fe989d8ec4d54d7416de2cb6301d6b87b897f4bfa33d1d03403e0968d83eec67`.
Separate original-case read receipt
`a7bdc39d3d448efbdf2711958ed2dea2aa74bb8b9ff0c7a8d970c414ad785a2a`
confirmed retained results and existing runtime witnesses. Independent source
review found no transport trust/lifecycle bypass. These are kernel fixture
results, not a successful Chrony integration.
A separate fixed read-only Tracking request actually sent exactly one104Byte
request through an exclusive abstract socket and received no reply within its
bound. Receipt `f82eef4fc7d8f7cab7971a835a68eef855f166c32cb2feaac191551188351881`.
Chrony4.8/4.9 source reconstructs the return Unix address as a C string; an
abstract name starts with NUL and is lost. This proves that the candidate
cannot provide the required reply transport with this implementation. No
additional AppArmor denial was observed in the filtered kernel audit.
The candidate is rejected for deployment. Its exact source and frozen six-test
proof are preserved as evaluation history. Production NativeTimeSource must
retain the prior named transport until a separately qualified compatible fix
is ready. No ARM64 build, signer, key, quality authority, client configuration
or RMM job was activated from this candidate.