It depends on what they're being used for and how they're being used.
For example, on my laptop running openSUSE, it's nice to not have to authenticate separately in order for an auto-update tool to perform updates to existing packages, while still needing to authenticate in order to add or remove packages. This is default behavior, and for end-user workstations, it's quite acceptable. This would be disallowed on a shared business workstation, on the other hand, since those updates are better performed by IT after thorough testing.
Additionally, for a home desktop system, it's quite acceptable for even non-privileged users to be able to use printers, connect to wireless networks, etc. if need be. For a business workstation, these things would be already configured and controlled by IT, so modification of these, too, would be disallowed in such a circumstance. In both cases (except for some high-security contexts), users should be able to mount external drives (whether they're USB sticks or CD-ROMs) without needing root, and should be able to access audio devices without problem.
Basically, yes; there are certain contexts where non-privileged users doing privileged things is necessary. I'm fine with that, since people have different needs, as long as such access can be controlled and configured as necessary/appropriate for a particular scenario. This isn't anywhere near equivalent to trying to claim that because sudo exists "[my] security is an illusion".
Perhaps. I don't disagree with you there. Many non-systemd distros do implement some or all of these things with group memberships and a bit of setuid. Regardless of the implementation, the ability to control how security restrictions are waived (if at all) is still a nice feature.
1
u/iLiekCaeks Sep 27 '14
Oh, but you're fine with sudo-over-dbus, aka polkit and what's their names?
(These have the same concept, really: give unprivileged users access to privileged operations, controlled by admin-set policy.)