12 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	acf075fa63	ssh-client keeps ~/.ssh to what it knows: sweep every other path into a kept folder (issue 1017, ADR 0415) ... ssh-client owns ~/.ssh, but treated every file it did not place as found, so a predecessor's drop-in and old copies stayed there for weeks. Its process now sweeps at start and every ten minutes: keys at any depth (and links to them), authorized_keys, authorized_keys2 and sockets stay, and a folder holding one is gone into; everything else moves to ~/.local/state/ssh-client/retired/<UTC time>/, a folder never shared with another sweep, with a list beside it, which ssh_client_check shows. Nothing is deleted.	2026-10-17 12:38:16 +00:00
mesh-tools	661b83249c	Give the forge an ssh name of its own, so it no longer merges with the operator's entry for its machine (issue 955, ADR 0409)	2026-10-17 00:01:42 +00:00
mesh-tools	ae9cda8531	Hand ssh-client's forge files to the provisioner client (issue 955)	2026-10-16 22:05:52 +00:00
fix-955-ssh	9cb615f121	Prove the forge key process over a real bus in the merge check (issue 955 S4)	2026-10-16 22:44:36 +02:00
fix-955-ssh	ad5a0f8e44	Place the forge's known host, SSH Host and git rewrite (issue 955 S3)	2026-10-16 22:43:51 +02:00
fix-955-ssh	a4cdd05cb2	Declare ssh-client's keys state and its forge-account requirement (issue 955 S2)	2026-10-16 22:43:29 +02:00
fix-955-ssh	b2009f1bb5	Keep the machine's forge SSH key and its keys entry (issue 955 S1)	2026-10-16 22:43:18 +02:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00
jochen	685cb1cb1b	Declare every module's data; the backup holder measures it (hq ADR 0233) ... Backup lines are derived from each module's data section instead of written by hand; the holder measures declared items, reads the array under them, and deletes a retired item only after a last restore point; the Go providers say each held consumer's size so an empty replacement is seen.	2026-10-06 16:47:49 +02:00
jochen	dde9c264f5	ssh-client: the mesh's region first in ~/.ssh/config, its hosts in config.d, tools in Go ... The region at the end let earlier Host lines win over the mesh's (research 027/03). A roster fact cannot be placed at the start, so the region holds one Include of config.d, and the hosts are config.d/00-mesh, read first. Eight tools; authorized_keys and known_hosts stay found until the controller holds those facts.	2026-10-04 12:38:40 +02:00
jschoubben	a19638d112	ssh-client: own ~/.ssh, not the openssh package ... A package has one owning module, and sshd already owns openssh on every node — assigning ssh-client was refused for both declaring it, and the refusal left every node unresolvable until it was unassigned. Owning it was wrong besides: unassigning ssh-client would have removed the package sshd serves from. The client binary ships in the package sshd holds.	2026-10-03 12:43:35 +02:00
jschoubben	301aeda5f3	ssh-client module: the mesh owns ~/.ssh, config from the hub (to-be 29) ... Requires openssh; creates ~/.ssh (0700, owned by the operator account via ${machine:account}); writes every other node's Host block (HostName + User <account>) into a marked region of ~/.ssh/config (home-scoped, into:block), so `ssh <node>` reaches each peer as the right account and the operator's own config is kept. Universal-tier: assigned wherever a person logs in; a node with no account gets no config.	2026-10-03 11:58:05 +02:00