http://bugzilla.opensuse.org/show_bug.cgi?id=1061707 http://bugzilla.opensuse.org/show_bug.cgi?id=1061707#c1 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert --- In my opinion, it is a bug in NetworkManager together with unfortunate defaults in KDE. My understanding is that NetworkManager specifies the particular policy that polkit will enforce. And it is using the policy for shared connections. It should, instead, use the policy for setting up a single connection. In any case, there's a workaround. Go into the connection editor in KDE. Edit this connection. Go to the security tab. Look at the field where you enter the connection key. There should be two icons to the right. One icon looks like an eye. The other looks like a diskette. Click on the diskette icon. There should be a choice for where the encryption key is saved. As I recall, the three choices are: save for single user (that's kdewallet), save unencrypted in a file, and enter the key each time. What you want is to save unencrypted in a file. The actual file where it is save is managed by NetworkManager, and readable only by root. So it isn't as risky as it sounds. You will need the root password to make these changes. But, once changed, you should not need the root password to connect in the future. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1061707 http://bugzilla.opensuse.org/show_bug.cgi?id=1061707#c3 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |wbauer@tmo.at Resolution|--- |DUPLICATE --- Comment #3 from Wolfgang Bauer --- This seems to be a design problem in NetworkManager itself AFAICT, it should not even ask for the privilege to *modify* the connection (which requires the root password) IMHO, especially as clicking on Cancel without entering the root password works as well anyway. The policy configuration is *not* wrong, changing it to allow all users to modify shared/system connections would just be a (insecure) workaround. And according to my knowledge, the security team rejected this anyway. The same thing happens in GNOME as well btw AFAIK... At least I remember a bug report about it not too long ago (closed as UPSTREAM or WONTFIX IIRC, can't find it at the moment though). Anyway, this is a duplicate of bug#971540. *** This bug has been marked as a duplicate of bug 971540 *** -- You are receiving this mail because: You are on the CC list for the bug.