On 08/13/2016 07:23 AM, Martin Schlander wrote:
Lørdag den 13. august 2016 10:20:35 skrev ianseeks:
If you are a single user machine, its not an issue. If you have multiple users logged into the same machine the its a big issue if one user can shut the system down while other people are working.
And how does crippling kshutdown a little bit solve that issue?
It doesn't. The sysadmin on that system will need to take other steps regardless if kshutdown is slightly crippled or not.
I take I that you're now admitting that an regular/ordinary (aka 'non privileged') user in a multi-user environment should not be able to shut down the multi-user environment. As for "crippling a little bit", I think you still fail to understand. Its not about 'crippling", and certainly not "a little bit". its about "completely removing the ability" for an ordinary user to shut down or kill another user's processes. AT ALL. IN ANY WAY WHAT SO EVER. If the sysadmins choose to do this by simply removing such programs, well that's one way, but that won't stop a user coding up and compiling his own program that does a kill(2). Better to use polkit and capabilities. There's no "slightly" going on in this kind of situation. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org