| 2012-06-26 22:12:57 |
James M. Leddy |
description |
Currently, the ubi-network dialog looks at WpaFlags (Wifi Protected Access) and RsnFlags (Robust Secure Network, aka: WPA2) to determine if the network is encrypted. According to Dan Walsh in this email, neither of these are used for WEP encrypted networks:
> You can't tell the difference between 64-bit and 128-bit WEP at all
because that information simply isn't available with WEP. You can only
tell that an AP requires "privacy" or not and that it does not use WPA.
For WEP the Privacy bit is the only thing you have.
https://mail.gnome.org/archives/networkmanager-list/2011-April/msg00191.html
I've experimentally verified that WEP doesn't work in ubiquity. If you choose a WEP ssid, the password box remains disabled, and clicking "Continue" causes nm-applet to pop up and prompt for the password. I wonder if this is still a concern though due to WEP being so infrequently used today. |
Currently, the ubi-network dialog looks at WpaFlags (Wifi Protected Access) and RsnFlags (Robust Secure Network, aka: WPA2) to determine if the network is encrypted. According to Dan Walsh in this email, neither of these are used for WEP encrypted networks:
> You can't tell the difference between 64-bit and 128-bit WEP at all
> because that information simply isn't available with WEP. You can only
> tell that an AP requires "privacy" or not and that it does not use WPA.
> For WEP the Privacy bit is the only thing you have.
https://mail.gnome.org/archives/networkmanager-list/2011-April/msg00191.html
I've experimentally verified that WEP doesn't work in ubiquity. If you choose a WEP ssid, the password box remains disabled, and clicking "Continue" causes nm-applet to pop up and prompt for the password. I wonder if this is still a concern though due to WEP being so infrequently used today. |
|
