The encryption template system wicd uses now is too confusing and inflexible

[Dan O'Reilly]

The system we use now for choosing the correct encryption is too complicated and inflexible. Right now when a user wants to configure the encryption they're greeted with this list:

WPA 1/2 (Passphrase)
WPA 1/2 (Preshared key)
WEP (Hex)
WEP (Passphrase)
WEP(Shared-Restricted)
LEAP with WEP
TTLS with WEP
EAP-FAST
PEAP with GTC
PEAP with TKIP
EAP-TLS

Which could be pretty daunting for an inexperienced user. Furthermore, if a user wants to use something like EAP-TLS, but needs to use a cert that isn't listed, or doesn't want a cert that is listed, he/she would have to create an entirely new template.

The system should be much simpler. We should make an effort to detect the type of encryption in use, and select it for the user by default. Additionally, it should be possible to omit credentials not needed, and all possible credentials should be accessible without having to creating a new template.

[stlubuntu (jlrbennett)]

Hey friends, great work on this wonderful application. Wicd has been a lifesaver for a great many users. Well done!

However, this bug is truly of "high importance" and is critical. Is there any chance of getting any action on this anytime soon?

http://stlouisubntu.myubuntunetwork.org/2010/10/03/how-to-connect-to-wep-encrypted-wireless-with-wicd-on-linux/

Please consider actually assigning this and stepping up the milestone target to the next stable release (such as 1.71 or 1.75 or something.)

[James Broadhead (jamesbroadhead)]

In particular; where wicd has detected a certain kind of encryption (eg. WEP), the menu in wicd-gtk should hide incompatible types of authentication mechanism. (