$ systemctl restart NetworkManager

$ systemctl restart NetworkManager
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to restart 'NetworkManager.service'.
Authenticating as: user
Password:

systemctl poweroff
Powers off immediately. Haha, wow.

Attached: (you) will defend this.jpg (1024x730, 100K)

>systemctl poweroff
>systemctl

yes?

Babby doesn't know about polkit rules. Babby doesn't know about local session types.

Fuck SystemDachau.

Attached: 2018-01-29-09_36_09-Watchdog-PAC-Preventable-YouTube-Internet-Explorer.jpg (900x494, 23K)

systemd users are basically cuckolds.

Does "knowing about polkit rules" make them less retarded?

Can you provide one (1) reason why this is good?
inb4 every use case must be laptop users because freedesktop bullshit

>systemd

If you don't like that, fucking change the configuration.
Nobody wants to enter their password and have permissions to turn their computer off. Also, it won't work if multiple users are logged in, or you're using a remote session; in that case you do need to have extra permissions.

poettering self-assigned this
poettering added the not-our-bug label
poettering closed this
...
poettering got cash from upstream (Red-Hat, CIA)

poettering referenced this issue

> Thanks for your detailed reply @poettering

I told you about systemd

poettering commented

(i sympathesize though, as I keep running into this myself actually all the time, but so far it didn't annoy me enough to do something about it. Hence by all means, please file a bug against polkit, and let's get this fixed there for good)

red hat basically specifics in their manuals to turn this off if wanted. also Debian.
gtfo kids

It just feels unpolished buddy.

Why require auth for restarting NetworkManager?

Because it's a system-level service, and you need permissions to do anything with those.
You can change the polkit rules to make those passwordless too.

ahahahah systemd ahahahahah

>Powering off the computer is not a system level service

Sure, but it's a compromise for usability.
You'd get more people complaining if it worked the other way.

I'm turning it off my removing polkit and systemd.
It's just easier to have sanity back than constantly cleaning up my configs after Poettering decides to change a major security settings for *everyone* by default again.

Ok, but I don't want to fuck with configs, I'd have stayed a ricer if this was the case.
I'm 300% more likely to want to restart networking because irl wlans are shitty than to fucking shut down my machine passwordless (which I can do on a physical level anyway).