You are not logged in.
Hello all,
When I put my workstation to sleep, I always run the command `gksudo systemctl suspend`, which presents a message box asking for my password, then puts the machine in suspend mode. Yesterday evening when I was wrapping up work for the day, I ran this command and instead received a notice from gksudo saying "Granted permissions without asking for password" and an explanation that I may be running it as root or something and not to worry. Well, I'm worrying because I don't know what caused this behavioral change.
This started yesterday after a system upgrade. I perform upgrades regularly, usually 3 times a week - so this isn't something from long ago.
On further investigation, I found that the `shutdown` command and the `systemctl suspend` commands can be run as my normal unprivileged user! The sudoers file remains unchanged (with a group entry for "%sudo ALL=(ALL) ALL". My uid, gid and group memberships also all remain unchanged.
I haven't used the shutdown command without sudo on this system ever, so that may not be a change (but seems strange nevertheless), but the systemctl issue is definitely new.
My question: has something changed in the official repos such that either:
A) gksudo now warns when it isnt needed, or
B) `systemctl suspend` no longer requires a privileged user?
Regards,
Ron
Last edited by rdahlgren (2015-07-22 15:23:01)
Offline
I just found this updated wiki entry from 4 days ago -> https://wiki.archlinux.org/index.php/Al … o_shutdown
Apparently this is new default behavior from systemd and polkit.
Marking thread as resolved.
Offline
Not a Sysadmin issue, moving to NC...
Offline