https://bugzilla.novell.com/show_bug.cgi?id=333684#c1 Mark Gordon <mtgordon@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com, hschaa@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |tambet@novell.com Severity|Normal |Enhancement Summary|(k)Networkmanager can't connect to 64bit |(k)Networkmanager can't use 64bit WEP |encrypted WEP - uses 128bit key |passphrase --- Comment #1 from Mark Gordon <mtgordon@novell.com> 2007-10-15 11:49:09 MST --- I believe this sheds some light on the subject: http://osdir.com/ml/linux.network.networkmanager.devel/2006-02/msg00006.html "40/64-bit passphrases are extremely dicey because there is no standard hash from passphrase to WEP key. Most manufacturers do it differently. 104/128-bit ones do have a (fairly) standard way." In the Windows world, I expect this is avoided by having the hardware vendor provide the driver, the hash, and various necessary glue. I further expect that the workaround under Linux is to use hex or ASCII, which both avoid the hash ambiguity associated with passphrase. Still, passing this along. Adjusting the summary to more accurately describe the problem and adjusting severity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.