Comment 37 for bug 344022

Bryan: I don't think that's a wpasupplicant problem, because the driver 1.8.0.0 works with WICD, and manual wpa supplicant configuration, and even NM 0.6 in Hardy and Debian Lenny. The problem is that NM 0.7 is TOO SMART, and it just assume that all kernel drivers are also as smart as it is. NM 0.7 removed the security option (TKIP / CCMP / AES etc) and just assume that wpasupplicant and the kernel driver should be smart enough to figure out which one to use.

Personally, I think it's a wrong decision to remove TKIP / CCMP choices in NM 0.7. You can just imagine how easy it's to add this in NM 0.7 (just a drop down in NM applet and some codes to write pairwise=TKIP in wpa_supplicant.conf), and how difficult it is to fix all those "stupid" drivers out there to adapt NM 0.7's smart policy.

And on the other hand, how could you blame the kernel drivers while all those drivers work with Wicd or NM 0.6, but not NM 0.7??? It will just force users leave NM and choose alternatives.

And finally, here is my case. I am connecting to company network WPA2/TKIP/MSCHAPv2. My test result is:
On Debian Lenny, rt2860sta 1.8.0.0, NM 0.6.6 works, Wicd works
On Ubuntu Jaunty, rt2860sta 1.8.0.0, NM 0.7 won't work, Wicd works
On Ubuntu Jaunty, rt2860sta 1.7.1.1, NM 0.7 works, Wicd works