4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	bf8f47ce66	Let ssh-client use the SDK's forgekey, and let the checks accept a module's own .ssh (issues 1480, 1484), part 2 of 17	2026-10-20 20:44:30 +00:00
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
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
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