Merge pull request 'sshd: the daemon it owns starts at boot' (#136 ) from fix/sshd-declares-the-daemon-it-owns into main

sshd: the daemon it owns starts at boot
The module said the service must be running and nothing about boot, so the machine's own way back in was enabled only because something before the mesh had enabled it. All four machines happen to be enabled today; none of them is enabled because the mesh says so, and a machine adopted tomorrow would run ssh until its first reboot. Not `state: running` alone for the same reason the module exists: this is the one daemon whose absence cannot be fixed remotely.
2026-09-28 19:43:29 +00:00 · 2026-09-28 21:43:27 +02:00 · 2026-09-28 18:48:26 +00:00
1 changed files with 1 additions and 0 deletions
@@ -31,6 +31,7 @@
      "type": "service",
      "unit": "sshd.service",
      "state": "running",
+      "boot": "enabled",
      "restart-on": [
        "config"
      ]
Author	SHA1	Message	Date
mesh-admin	521a8dd1e2	Merge pull request 'sshd: the daemon it owns starts at boot' (#136 ) from fix/sshd-declares-the-daemon-it-owns into main	2026-09-28 19:43:29 +00:00
jschoubben	e145e2236c	sshd: the daemon it owns starts at boot The module said the service must be running and nothing about boot, so the machine's own way back in was enabled only because something before the mesh had enabled it. All four machines happen to be enabled today; none of them is enabled because the mesh says so, and a machine adopted tomorrow would run ssh until its first reboot. Not `state: running` alone for the same reason the module exists: this is the one daemon whose absence cannot be fixed remotely.	2026-09-28 21:43:27 +02:00
mesh-admin	4d7e37e319	Merge pull request 'fail2ban bans through an action every machine has' (#135 ) from fix/fail2ban-bans-through-what-every-machine-has into main	2026-09-28 18:48:26 +00:00