#10385 NORM Not Tri: Sugar may store invalid WEP keys by accident, make it impossible to access an AP

[Zarro Boogs per Child]

#10385: Sugar may store invalid WEP keys by accident, make it impossible to access
an AP
-----------------------------+----------------------------------------------
 Reporter:  greenfeld        |                 Owner:  dsd          
     Type:  defect           |                Status:  new          
 Priority:  normal           |             Milestone:  Not Triaged  
Component:  network manager  |               Version:  not specified
 Keywords:                   |           Next_action:  never set    
 Verified:  0                |   Deployment_affected:               
Blockedby:                   |              Blocking:               
-----------------------------+----------------------------------------------
 This may be a variant or close relative to issue #9977.

 Sugar may store invalid WEP keys by accident in connections.cfg, and make
 it impossible to access an 802.11 Access Point using said WEP key without
 manually editing or clearing out connections.cfg.

 This has been reproduced in both 10.1.2 as well as Fedora Beta 14/Sugar
 0.90, which for some reason I have had better luck reproducing this with.

 Reproduction:
  1. Setup a WEP 128(104)-bit encrypted access point with a known hex-style
 key.
  2. Attempt to connect to it from the Sugar network view.  You should be
 prompted for the encryption key.
  3. Set the type of key to enter to Hex (not Passphrase) in the dropdown
 menu.
  4. Enter "Hello" in the field and press the Enter key {even though "OK"
 should be grayed out and "Cancel" the only choice, as Hello is not a valid
 Hex number with an acceptable length}.

 Expected: The connection attempt is aborted; Sugar goes back to trying to
 use whatever its previous favorite AP/mesh/ad-hoc network was.

 Actual: The connection attempt goes on until Sugar decides to try
 something else.  Restarting the computer and/or attempting to access the
 AP setup in Step #1 will always fail.

 ~olpc/sugar/default/nm/connections.cfg will have a line for the AP setup
 in step #1 that says "key = Hello".  This will cause messages to be logged
 to /var/log/messages that wep_key0 is invalid every time one tries to use
 this AP, causing Network Manager to try and go on to the next available
 preferred system almost immediately and never successfully prompt again to
 get the necessary updated key information.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10385>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system