If you mean code for OpenPAM is not portable then there isn't much need for portability when you write a WiFi manager for FreeBSD. And you can integrate it to QT/GTK apps.
If you mean code for OpenPAM is not portable then there isn't much need for portability when you write a WiFi manager for FreeBSD. And you can integrate it to QT/GTK apps.
Sorry, but you fail to see the added benifits of ConsoleKit. With ConsoleKit you get a framework to assign users different privileges. Like changing WiFi settings i.e. Sure this can be done using PAM but ConsoleKit makes this so much nicer and more fine grained. It's more or less how Windows Group Policies work.
There's a rather big difference between authenticating a user and authorizing a user. PAM takes care of the authentication while ConsoleKit/PolicyKit can take care of the authorization. Why would a user need to authenticate again when that user's already logged in? ConsoleKit/PolicyKit can authorize that user to use that function, no need for passwords, popups or whatever.
Why would a user need to authenticate again when that user's already logged in? ConsoleKit/PolicyKit can authorize that user to use that function, no need for passwords, popups or whatever.
User needs to authenticate because he needs to do something that only root is allowed to and if you let normal users do that without authorization every time then its not that secure ain't it?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
