http://bugzilla.novell.com/show_bug.cgi?id=498284 User jmatejek@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498284#c2 --- Comment #2 from Jan Matejek <jmatejek@novell.com> 2009-07-02 07:12:03 MDT --- i'm installing M3 now, but from what you wrote, i'm pretty confident that the original bug is not fixed. to clarify: by "WEP key" in the following text, i mean 40-bit or 104-bit number which, concatenated with a 24bits random IV value (thus forming 64bit or 128bit key respectively), is used to encrypt the wireless packets. in traditional iwconfig interface, you can enter this key either as a sequence of 10 or 26 hex digits, or via "s:" syntax as a sequence of 5 or 13 ascii characters, whose bytes are then concatenated to form the desired n-bit sequence what i see now in my M1 networkmanager dialog are the following choices (roughly translated to english from my localized version): * WEP 40/128bit key --> this means that the user is required to input 10 or 26 hexadecimal digits, which are then used directly as a WEP key * WEP 128-bit passphrase --> i am not sure what this is, but from my observation, it seems that the passphrase (length and character types aren't limited) is run through some kind of hash function and output of that is used as the WEP key * LEAP * Dynamic WEP (802.1x) --> those two don't apply for "plain" WEP keys what is missing is the option that was there before -and- that should IMO be the default: * WEP 40/128bit ascii key --> user needs to input 5 or 13 ascii characters, which are then directly used as a WEP key, similar to iwconfig's "s:" syntax this is actually the option that is in widespread use, and not having it is rendering NetworkManager (and conversely Linux as a whole) completely unusable for a wide range of public WEP encrypted networks now, is this "ascii key" option present in M3 ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.