On 12/04/18 00:17, Frederic Crozat wrote:
Le mercredi 11 avril 2018 à 23:03 +0930, Simon Lees a écrit :
On 11/04/18 20:57, Frederic Crozat wrote:
Le mercredi 11 avril 2018 à 11:16 +0200, Carlos E. R. a écrit :
On Tuesday, 2018-04-10 at 19:46 +0200, Carlos E. R. wrote:
On Tuesday, 2018-04-10 at 15:45 +0200, Richard Brown wrote:
On 10 April 2018 at 15:39, Peter Suetterlin <> wrote:
> (*) My other point mentioned in another reply, the > availability of net > connection without someone being logged in, *is* such > a > showstopper > though.
The default network manager interfaces connect just fine without a user being logged in. In all my tests, NetworkManager already does this just fine, and already has for quite some time (at least every Leap release to date). Obviously if this doesn't work it would be a bug that needs to be addressed, but I don't think we should assess the feasibility of features we could have today on the possibility of bugs which do not seem to have today.
Sorry, not true.
I just went to my laptop to do the test in 15.0: I logged out of my session in XFCE, went to the console, used "if addr" and the wlan had lost the IP. I can not post the command output, no network there now.
I know how to make it work (perhaps), but then, that is not the default config.
Later I thought to test the cable, so I connected it without login, and it worked. Why this connection works by default and not the other, I don't know; maybe it is related to needing a password.
Then there is the setting "use this connection by other users" or similar wording, which is a manual action that I haven't done in that setup. It then requires the root password to configure.
And it is expected. Wifi credentials are "personal" by default (they might contain data you don't want to be visible by everybody on the system) and not shared unencryted in /etc/NetworkManager.
If you want to get the wifi credentials available system-wide, you have to do a conscious decision.
I have a polkit file that allows any user in the "network" group to modify the system network settings, which is my way around this issue if others find it useful I don't see why it couldn't go into its own small package.
There is no such thing as a "network" group in default install and then, the next question to ask is how to populate it.
The package could create the group so that isn't hard, by default the group would have no users and we would update our documentation to say something along the lines of "If you would like your user to be able to set the system network settings which will also allow your network connection to start at boot up add your user to the 'network' group" Someone could make a reasonable argument that on tumbleweed atleast adding all users (or atleast the one created in the installer) to the network group would make sense. But i'm not going to argue either way on that adding my user to that group doesn't take long and its something I do shortly after a fresh install anyway. If anyone is interested here is the rule file below. tek-top:~ # cat /etc/polkit-1/rules.d/50-org.freedesktop.NetworkManager.rules polkit.addRule(function(action, subject) { if (action.id.indexOf("org.freedesktop.NetworkManager.") == 0 && subject.isInGroup("network")) { return polkit.Result.YES; } }); -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org