|
|
|
|
|
|
by TacticalCoder
728 days ago
|
|
|
As I run a system similar to the one used in TFA I'll give my take... > So what happens if ssh (IIRC correctly in typical configurations it depends on network to start) fails to start at boot? I do this for my main desktop. If the worse of the worse happen, I've got backup of everything (we all do right?) and I re-install the system. What I mean is: what do you do when you SSD is dead? You can't even login at failsafe console either. In 30 years of using Linux I've have hard disk die on me way more than I had my sshd daemon not starting. The ratio is even a divide-by-zero error. Arguably if my OS had its sshd daemon randomly not starting, it'd be an indication to me that it's time to move to a more stable OS. > What does this actually buy us over sudo or su? Much harder to pull local privilege escalation exploits. |
|
|
That's not certain. sshd is way bigger than sudo, so chances of it having an exploitable bug seem higher.