Summary: | "WEP Passphrase" doesn't work correctly - or is unintuitive to use | ||
---|---|---|---|
Product: | knetworkmanager | Reporter: | Dima Ryazanov <dima> |
Component: | wep | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 0.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dima Ryazanov
2007-02-28 23:12:56 UTC
The algorithm for passphrase encoding is 'take the md5sum of the passphrase, then convert that to hex, then take the first 10 or 26 digits, repeating as needed'. So it provides enough hex to create the key.
What is the hex key as sent by knetworkmanager (use iwconfig to see) and how does it compare to the actual hex key needed?
> Also, would it be more intuitive if the other two options were combined? So > knetworkmananger would choose "ascii" for 5/13 character passwords and "hex" > for 10/26 ones.
Yes, good point.
> The algorithm for passphrase encoding is 'take the md5sum of the passphrase, then convert that to hex, then take the first 10 or 26 digits, repeating as needed'. So it provides enough hex to create the key.
Do any other programs use that algorithm? (I've never seen it before.)
In order for it to be useful, the access point should allow entering passwords the same way, right? But all access points I've seen so far only allow hex or ascii. Also, same with Windows and, I think, OS X.
Maybe it shouldn't be the default option, and there should be some explanation for it...
Every wireless manager I have used for Windows and OS X allows passphrases, and they are the default in the built-in network managers in Windows XP and OS X. All APs and routers that I have handy, including a handful from linksys, netgear, and d-link allow passphrase entry. Except for myself, every person that I know with a WEP-protected network uses a passphrase, and most have no idea what a WEP key is. Not sure where the confusion is coming from here. Passphrase works in KNetworkManager 0.7 |