On 2020-07-03 12:32, ToddAndMargo via users wrote:
On 2020-06-30 21:47, Ed Greshko wrote:
> On 2020-07-01 12:42, ToddAndMargo via users wrote:
>> Thank you!
>>
>> $ nmcli connection show eno2 | grep perm
>> connection.permissions: --
>>
>>
>> What does "--" mean?
>
> It means "no user restrictions". It means any user can up/down the
connection via nmcli.
>
Huh.
Works:
$ /usr/bin/nmcli c up eno2
Does not work:
$ /usr/sbin/ifup eno2
$ /usr/libexec/nm-ifup eno2
I know that is what you said, but was it intended
to be restricted to nmcli?
The answer to why nmcli works for a user while the other 2 shell scripts fails was alluded
to by "Tom H".
(Of course there really is only 1 shell script).
The answer is polkit. If you were to enable logging/debugging for polkit you'd get
Jul 03 13:03:19
f32k.greshko.com dbus-broker[678]: A security policy denied :1.70 to send
method call
/org/freedesktop/NetworkManager/Settings:org.freedesktop.NetworkManager.Settings.LoadConnections
to :1.13.
which coincides with the first command (nmcli connection load) in the shell scripts.
--
The key to getting good answers is to ask good questions.