News for hackers. Stuff that matters.

A comment on Heap-based buffer overflow in Sudo. Parent comment

Re:Heap-based buffer overflow in Sudo by GoblinSlayer on Wednesday January 27, 2021 @01:57PM (#25932270)
I want to start and stop a couple of systemd services remotely. Currently I expose the command with sudo and run it under a remotely connected user. What are other options?
[ Parent | on HN ]
Re:Heap-based buffer overflow in Sudo by Spivak on Tuesday February 09, 2021 @10:57AM (#26078969)
You don't actually have to be root at all to manage systemd services. If you give the user `org.freedesktop.systemd1.manage-units` in Polkit then they can just run systemctl as their user and it will work.

If you only want to allow specific units the authorizer is passed the unit under `action.lookup("unit")`.

[ Parent | on HN ]
Re:Heap-based buffer overflow in Sudo by ktpsns on Wednesday January 27, 2021 @02:24PM (#25932651)
In your case either use plain /sbin/su: https://man7.org/linux/man-pages/man1/su.1.html or login via root. Your use case sounds very sudo-like, thought. Probably stick to sudo.
[ Parent | on HN ]
Re:Heap-based buffer overflow in Sudo by GoblinSlayer on Wednesday January 27, 2021 @04:21PM (#25934112)
It's a batch job. Ah, I see it mentions runuser, will check it.
[ Parent | on HN ]