summaryrefslogtreecommitdiff
path: root/data/templates/ssh/override.conf.tmpl
AgeCommit message (Collapse)Author
2021-01-18ssh: T3212: remove RestartPreventExitStatus from systemd unitChristian Poessinger
When configuring SSH to only run inside a given VRF the system can not start SSHd on bootup as the Kernel will report EPERM (Operation not permitted) when loading the VRF BPF program. This returns the exit code 255 which is marked in the systemd unit file to stop restarting the service forever. Removing this limitation will restart the SSHd on startup and it will live inside the VRF till the end of days. (cherry picked from commit cdbac8f10b470a06aff54832da7f006aa3ed194e)
2021-01-13ssh: T3212: do not make /run/sshd directory disappear on failureChristian Poessinger
(cherry picked from commit 57fca79636b783dc4be2df1bc1ff12a0ce79d988)
2020-08-03ssh: T1076: make configuration volatileChristian Poessinger
Move sshd_config file to /run so it must be generated on every boot and is not stored accidently.
2020-07-04ssh: vrf: T2682: support restart on failure indefinitelyChristian Poessinger
Linux tries to bind sshd to the VRF but it is yet not ready - for any arbitrary reason. After restarting SSH to often (rate-limiting) it is blocked by systemd. Using Restart/RestartSec is not enough - systemd services use start rate limiting (enabled by default). If service is started more than StartLimitBurst times in StartLimitIntervalSec seconds is it not permitted to start any more. Parameters are inherited from DefaultStartLimitIntervalSec (default 10s) and DefaultStartLimitBurst (default 5).
2020-07-04ssh: T2682: simplify VRF bindingChristian Poessinger
2020-06-11ssh: T2321: add VRF supportChristian Poessinger
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 04:09:03 +0000