vyos-1x.git/data/templates/ssh/override.conf.tmpl, branch feature/T9082-codeql-cppVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp2022-04-14T19:34:52+00:00ssh: T4353: fix Jinja2 linting errors2022-04-14T19:34:52+00:00Christian Poessingerchristian@poessinger.com2022-04-14T19:34:52+00:00urn:sha1:dbfc2add3434638628b43ecfa097fbd166c85db7ssh: T4333: migrate to new vyos_defined Jinja2 test2022-04-11T04:05:12+00:00Christian Poessingerchristian@poessinger.com2022-04-11T04:05:12+00:00urn:sha1:5f164e59aac8ce7b8eba50d3906da87a3bb7a9dassh: T3212: remove RestartPreventExitStatus from systemd unit2021-01-18T16:50:55+00:00Christian Poessingerchristian@poessinger.com2021-01-18T16:50:55+00:00urn:sha1:cdbac8f10b470a06aff54832da7f006aa3ed194e
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.
ssh: T3212: do not make /run/sshd directory disappear on failure2021-01-13T20:40:36+00:00Christian Poessingerchristian@poessinger.com2021-01-13T20:40:36+00:00urn:sha1:57fca79636b783dc4be2df1bc1ff12a0ce79d988ssh: T1076: make configuration volatile2020-08-03T16:40:06+00:00Christian Poessingerchristian@poessinger.com2020-08-03T16:38:55+00:00urn:sha1:ca2ab503f42a8446175954e9e7280ecc8e75e927
Move sshd_config file to /run so it must be generated on every boot and is
not stored accidently.
ssh: vrf: T2682: support restart on failure indefinitely2020-07-04T19:36:51+00:00Christian Poessingerchristian@poessinger.com2020-07-04T19:34:37+00:00urn:sha1:8c4221083d8898bf478e2aeec04dd135e4993cb1
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).
ssh: T2682: simplify VRF binding2020-07-04T19:36:51+00:00Christian Poessingerchristian@poessinger.com2020-07-04T19:22:29+00:00urn:sha1:ff7dd3b9de82347cc77612cb79dc159661320d49ssh: T2321: add VRF support2020-06-11T13:58:18+00:00Christian Poessingerchristian@poessinger.com2020-06-11T13:58:18+00:00urn:sha1:5deb12c509bea6e353c3b4c3174f040895646cf8