Seriously, we have dbus, and NetworkManager from Gentopia used that to deploy a valid policy. Just use the "plugdev" group for that stuff. It's a nonsense???!
I am sorry you disagree with our decision to use pam_console rather than rely on people having to write files to /var/run/console/$username - we went for ease of use rather than for making sure you are in a specific group. Patches are always welcome, but this is a design choice, and not a bug.
this is an OLD and BAD design choice. at_console is broken by definition. the RIGHT way is using dbus.
I'm not much sure how NetworkManager works, but as far as I understand, it's possible to use an alternative method to give permission to users to change the configuration, that wouldn't involve pam_console. Considering that them PAM team (that at the moment consists of... me? but that's not just me, I can tell) already told in the past that pam_console is barely supported, it's an hack, its implementation leave to desire and so on, if it would be possible to use the plugdev group for authentication (as it's done for pmount) rather than pam_console, it would be a good improvement. The pam_console method, for who likes it, can be conditioned to a pam_console useflag as it was present in sys-libs/pam-0.78, and disabled by default. Steev, is this feasible?
thank you guys and don't worry to ask me to help you in that. I really want pam_console out of NetworkManager stuff.
Per metalgod this is fixed.
great :) going to test that asap :)
