#1602 closed defect (fixed)
can't connect to WEP shared key networks
| Reported by: | dsd | Owned by: | tomeu |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Unspecified | Keywords: | r+ |
| Cc: | sascha_silbe | Distribution/OS: | Unspecified |
| Bug Status: | Assigned |
Description
Sugar's model.network is only communicating the need for shared key authentication in the secrets response, which is too late for NM to do anything about it. This means that all connections to shared key WEP networks fail.
This isn't trivial to fix, as the only point at which the user can scream "I want shared key authentication" is when sugar pops up the key request dialog, which is already after the WirelessSecurity details have been sent.
Attachments (1)
Change History (8)
comment:1 Changed 14 years ago by dsd
comment:2 Changed 14 years ago by sascha_silbe
- Cc sascha_silbe added
comment:3 Changed 14 years ago by dsd
- Keywords r? added
Dan Williams suggested a solution:
http://mail.gnome.org/archives/networkmanager-list/2009-December/msg00018.html
This works. patch coming up.
Changed 14 years ago by dsd
comment:4 Changed 13 years ago by erikos
- Bug Status changed from Unconfirmed to Assigned
- Keywords r+ added; r? removed
- Milestone changed from Unspecified by Release Team to 0.88
Thanks for working that out (with looking for advice upstream)!
The patch looks good. Please add your copyright as well in into the header of the files and in meshbox.py you have a line too long error. For example make it:
settings = kwargs['connection'].get_settings() net.create_keydialog(settings, kwargs['response'])
Would be nice to add a little test case, so people can test when it gets available in the form ( http://wiki.sugarlabs.org/go/Development_Team/Release#Stabilizing ).
I guess backporting to 0.84 and 0.86 shouldn't be an issue at all.
comment:5 Changed 13 years ago by dsd
|TestCase|
Attempt to connect to a WEP network "protected" with shared key authentication, ensure that connectivity succeeds.
comment:6 Changed 13 years ago by dsd
- Resolution set to fixed
- Status changed from new to closed
I wonder if NM can be more flexible and accept only learning about the auth alg late in the game. http://mail.gnome.org/archives/networkmanager-list/2009-December/msg00011.html