Can not connect using WEP ASCII keys

Bug #453260 reported by Jonathan Riddell
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
knetworkmanager
Fix Released
Medium
plasma-widget-network-manager (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Karmic by Störm Poorun

Bug Description

Binary package hint: plasma-widget-network-manager

knetworkmanager can not connect using WEP ASCII keys (which are different from Hex or passphrase). This is because there is no standard hex to ascii mapping.

Jonathan Riddell (jr)
Changed in plasma-widget-network-manager (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Störm Poorun (subs-olan) wrote :

I appreciate the difficulties with 64bit WEP ASCII keys.

However, networkmanager itself (as well as Windows systems and MacOS, and Gnome using networkmanager) all permit the user to attempt to connect.

WEP ASCII keys are very common, including in public wifi networks.

Most users either a) cannot obtain the hex equivalents (e.g. in a public networks), b) do not know why their connections have failed, c) do not have the knowledge or information, or internet access, to find out why.

Having no capability to enter and attempt connection using WEP ASCII keys is therefore a major regression in the implementation of networkmanager.

I submit that it is preferable to permit a user to attempt connection
using the algorithms that were formerly permitted, albeit with a warning
message that WEP ASCII usage is deprecated and may not work. Even if it doesn't work with
half the connections it is not rational to deny any attempt at connections via this
method.

In any event, I would suggest that when a user attempts to enter a 64bit WEP
key, rand it can't connect, rather than just having their connection refused, a message should display
explaining why their connection isn't working, and what they may do to about
(get a HEX key, or use WPA for example).

This would at least prevent some users worrying what was going wrong with their
computer, and attempting all kinds of fixes (aggravated further since they may
have no internet connection to research the problem, and if their WEP key and
connection used to work fine with Gnome, KDE ,or Windows).

Revision history for this message
Aurélien Gâteau (agateau) wrote :

I created a patch to add support for WEP ASCII keys. Can you try this PPA?

https://launchpad.net/~agateau/+archive/ppa

Revision history for this message
Störm Poorun (subs-olan) wrote :

Many thanks! I've tested it on a couple of routers and public wifi network and can confirm that it works fine with WEP ASCII keys.
(Running plasma-widget-networkmanagement from Aurélien's ppa repository on Kubuntu Karmic Beta 64bit.)

[Unfortunately, one little snag, which warrants a separate bug - when I get the chance I'll search/create a new bug for KDE. The default for the software on connecting to a WEP network is to ask the user to enter a WEP passphrase rather than a WEP ASCII or HEX key. I realise that there's no way of the software differentiating between passphrases and keys, but that there is a way of differentiating between different ASCII and HEX keys. Thus the user must at least choose either key or passphrase, the rest is figured automatically.
I suggest it would be far better for a request for a key to be the default, because: a) the vast majority of WEP usage is via ASCII or HEX keys rather than passphrases - as (from broad anecdotal experience, and market rationale) consumer devices and public networks to not default to using WEP passphrases; b) the few usages of WEP passphrase almost always involve technical users or users in corporate spheres with either technical support or a far greater awareness then the general public of 'having to do something special' with their wifi settings. ]

Revision history for this message
BryanLawrence (b-n-lawrence) wrote :

I just tried this, the ppa works, insofar as I can enter my password in the key box, and my intel 3945ABG can associate ... but dhcp doesn't work (it does fine on the same network using 8.04 fine for ethernet to the same router using 9.10 kubuntu RC1, and it doesn't seem to work from the command line either).

I guess I need to raise the dhcp issue as another bug ... it seems a never ending series of problems just to get wireless working :-(

However, I agree with Störm that this is a major regression unless it sorted by default, and with an intuitive prompt ... like it or not, these short ascii wep keys are everywhere ....

Changed in knetworkmanager:
status: Unknown → Fix Released
Revision history for this message
naught101 (naught101) wrote :

Fix released? This still doesn't work for me...

Changed in plasma-widget-network-manager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
paddy (paddy-piments) wrote :

where's the fix , where's the release.

I have a totally upto date kubuntu and it is still unable to accept an ascii WEP needed by my router.

Am I supposed to wait for the next major release of kubuntu or is this still not fixed?

Revision history for this message
Rohan Garg (rohangarg) wrote :

weird this happens with numeric keys as well!

Changed in knetworkmanager:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.