←back to thread

466 points CoolCold | 1 comments | | HN request time: 0.2s | source
Show context
cesaref ◴[] No.40214754[source]
Let's assume for a moment that it is lower risk than sudo (which is the problem is it addressing), why isn't it also called 'sudo', designed to behave the same as the thing it is replacing, so that anyone (and any scripts) that currently use sudo can carry on and be oblivious to the security benefits this new implementation offers?

I'd instead like to see a post saying something like 'on systemd based systems, a more secure implementation of sudo is provided', and all the clever whatever it is happens behind the scenes, and frankly i'll never need to know about it.

replies(4): >>40214805 #>>40215032 #>>40216182 #>>40217446 #
1. voiper1 ◴[] No.40215032[source]
calling it sudo would create the expectations that all the options, config, and usage is exactly the same.

It would appear that it's _functionally_ the same, but using a different mechanism and with a new name so they don't want to be locked down to all the other stuff.