kde network manager and pam_mount

[Rob Verduijn]

Hello Will,

You are right, I should have written it down in a different way.

wicd did not solve my pam mount problem, traditional network
management did that.
Traditional network management already launched the network
connection, so that when the graphical login appeared and the user
credentials that are supplied pam_mount picks them up.

wicd merely provides a way for users to still select a different
network than the one I configured
wicd allows the network admin to make a central wifi network
configuration so that I do not need to configure a wifi network for
each user that makes use of the laptop.
wicd does not provide networked authentication, on the other hand wicd
does not make it impossible to use networked authentication. It is
actually very easy to get it to work in combination with wicd.

Still kde network manager and/or network manager need to be able to do
the right thing and simply work in the previously mentioned situations
without the need of homebrew scripts in
/etc/NetworkManager/dispatcher.d(the default for wired connections in
opensuse

I like the way knm/nm are going but I think they still need some work.

My apologies if I have insulted anyone with my previous mail.
Rob Verduijn


2010/4/5 Will Stephenson <wstephenson at kde.org>:
> On Monday 05 Apr 2010 14:11:12 Rob Verduijn wrote:
>> I implemented a solution a couple hours ago. Somebody told me to try wicd.
>>
>> The drawback of wicd is that I must diverge from the default opensuse
>> configuration (which uses kde network manager)
>> This means the wicd solution will bite me at some time in the future
>> because it's not the default in opensuse.
>>
>> Solution:
>> Switch back to traditional network configuration (ie ifup/ifdown)
>> Define a default wifi connection.
>> Install wicd http://wicd.sourceforge.net/
>>
>> advantages:
>> users can still select a different wifi network if they wish to.
>> It is possible to use ldap/ads/networked authentication mechanism.
>> it works with pam_mount
>> Does not need the wifi configuration added for each additional user
>> that for some reason uses the laptop on the same wifi network.
>>
>> drawbacks:
>> not standard included in opensuse 11.2 (available in the opensuse build
>> service) possible future compatibility issues.
>>
>> I'll keep an eye on the (kde) network manager mailing list to see if
>> the features get added some time in the future.
>
> For the record, how does wicd support pam_mount?  directly or via a general
> purpose user session based on connection change hook?
>
> Will
> _______________________________________________
> kde-networkmanager mailing list
> kde-networkmanager at kde.org
> https://mail.kde.org/mailman/listinfo/kde-networkmanager
>