WPA status 2005-12-14

[Dan Williams <dcbw redhat com>]

Where do we stand?

o Access point capabilities are parsed from scan data including WPA and
    RSN information elements, if the driver provides them
o Device/driver capabilities are discovered if the driver provides them
o The applet hashes keys for the different security methods
o The applet passes all the necessary security parameters to
    NetworkManager when you choose "Other Wireless Network..."
o NetworkManager receives security parameters from the setActiveDevice
    call and currently does nothing with them


What is still left to be done?

o Convert the passphrase dialog to use the new cipher stuff like the
    Other Network dialog does
o Push the NMAPSecurity objects into NMAccessPoint objects and make
    device activation actually use them
o Expose access point and device capabilities via DBUS
o Make the applet respect access point and device capabilities (ie,
    don't allow WPA on non-WPA-capable devices)
o Remove key hashing code from NetworkManager (will be obsoleted by
    NMAPSecurity objects anyway)

Further out:
o Make the dialogs look prettier (perhaps hide the auth method stuff
    behind an "Advanced" button or an expander like OS X does)
o Create a supplicant_manager object that controls invocations of
    wpa_supplicant
    o Write out correct wpa_supplicant config file and ask the
        NMAPSecurity objects to write out their security information
    o Connect to wpa_supplicant's control socket to monitor association
        status

NetworkManager HEAD will likely be in high-flux in the next week and
probably won't work correctly.  We should try to at least keep it
buildable, but it's likely that the D-BUS API will be trashed until
things settle down, which is almost as bad.

Dan