You are not logged in.
- Topics: Active | Unanswered
#1 2022-01-29 00:42:01
- Rommy
- Member
- Registered: 2014-10-17
- Posts: 51
iwd 1.23-1 changes D-Bus policy
Since iwd 1.23-1 it can be possible, that you cannot start `iwctl` as your logged-in user.
Adding the group `netdev` and adding allowed users to it, allows access again.
Offline
#2 2022-01-29 02:42:37
- CarbonChauvinist
- Member
- Registered: 2012-06-16
- Posts: 413
- Website
Re: iwd 1.23-1 changes D-Bus policy
That's a debian specific note though, furthermore I have no issues starting iwctl with iwd 1.23-1.
I don't even know if that group exists under Arch and with systemd it can cause more problems than it potentially addresses to add yourself to random groups. If you're having issues I'd check to make sure your session is not borked.
FWIW, I'm only a member of the following groups and again have no issues starting iwctl as expected:
~ $ groups
wireshark realtime libvirt kvm wheel <username>"the wind-blown way, wanna win? don't play"
Offline
#3 2022-01-29 21:44:39
- progandy
- Member
- Registered: 2012-05-17
- Posts: 5,296
Re: iwd 1.23-1 changes D-Bus policy
That's a debian specific note though...
Doesn't matter since the upstream project makes that change in the generic distribution agnostic files as arch simply uses the upstream config here.
I don't even know if that group exists under Arch ...
It does not exist, so you'd have to create it.
furthermore I have no issues starting iwctl with iwd 1.23-1
Your user is in the wheel group which has access as well.
Last edited by progandy (2022-01-29 21:48:27)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
#4 2022-01-30 13:05:19
- CarbonChauvinist
- Member
- Registered: 2012-06-16
- Posts: 413
- Website
Re: iwd 1.23-1 changes D-Bus policy
Thanks for the clarifications progandy, I assumed that the wheel group is what was giving me access.
I rereading OP again, they also noted that the `netdev` group would have to be added too.
So in Arch's case what would best practice be? From my perspective, for desktop linux cases, if the user is already a part of the superuser (i.e. `wheel`) group that seems ideal. I can't imagine a scenario where one would need to be in a newly created `netdev` group but wouldn't also want to be in the `wheel` group? But I guess it depends on the use case/needs.
"the wind-blown way, wanna win? don't play"
Offline
#5 2022-01-31 10:56:46
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 14,574
Re: iwd 1.23-1 changes D-Bus policy
I have never enabled/used/needed the wheel group , but there are cases where a normal user needs to have root rights for a specific task .
IF iwd / iwctl were used on a system I own/maintain making some users members of netdev could be an acceptable alternative.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#6 2022-01-31 16:29:45
- Rommy
- Member
- Registered: 2014-10-17
- Posts: 51
Re: iwd 1.23-1 changes D-Bus policy
I can't imagine a scenario where one would need to be in a newly created `netdev` group but wouldn't also want to be in the `wheel` group? But I guess it depends on the use case/needs.
Exactly. I don't use the root user per default and I don't want my daily user to be able to get root permissions. I very often need to change wifis (to have access to different subnets/machines), to test stuff and so on, getting root every time is not acceptable for me. So giving my user the least privileges fits my needs best.
Offline