Jon Escombe <lists <at> dresco.co.uk> writes: > I've found an issue which I think may be at the root of all this.. > > nm_ap_security_new_from_ap() appears to match on *any* of the capabilities > defined for each encryption type. In my case, my WPA2-EAP network was being > configured as a WPA2_CCMP_PSK network, due to the presence of the > NM_802_11_CAP_PROTO_WPA2 capability. I believe the attached patch solves > this > problem by requiring the reported capabilities to match *all* of the defined > capabilities. > > I can test further when I'm back in the office tomorrow, but I'm hopeful > that is > what was preventing the stored credentials from being retrieved.. > > Regards, > Jon. >
The patch fixes the network detection, so that it's properly seen as WPA2-EAP, but doesn't help with my overall problem. nm_dbus_get_user_key_for_network() requests a key, but the callback is never entered.. Any suggestions for debugging this part? Thanks in advance, Jon. _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
