Re: Braindump on wpa_supplicant

Dan Williams <dcbw redhat com> writes:

> Well, I'm talking about the whole thing, where we get to modify wpa_supplicant 
> for slave mode and what not as well.  We don't want to simply let wpa_supplicant 
> loose, since _NetworkManager_ is the program that's determining which network to 
> connect to, what password/passphrase/key to use, what certificates
> to use, etc.  

This should be possible with current wpa_supplicant, since you can
restrain it on a specific network ID.

> And I'm not going to write out a config file for wpa_supplicant, that's just 
> bogus.  This stuff needs to be tightly integrated, not writing config files for 
> stuff all over the place.  The only reason we do that for 
> named/caching-nameserver is because it wasn't dbus-enabled yet at the time we 
> did the VPN stuff (it has since been made dbus-aware).

So, will you try to make wpa_supplicant dbus-aware?
The current socket interface is quite fine, but only one program can
listen to events.

Olivier Blin
Mandrakesoft becomes Mandriva

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]