#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
         Resolution:                   |    Keywords:               
        Next_action:  never set        |    Verified:  0            
Deployment_affected:                   |   Blockedby:               
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by dsd):

 Maybe you'll still argue that the behaviour is wrong, but this is at least
 a little bit debatable.

 The problem is that there's no way for the client to know if the
 connection failure was due to bad WEP key, or if the WEP key was correct
 but there was a network problem preventing the machine from obtaining a
 DHCP address (e.g. school server unplugged). The 2 situations appear
 identical to the XO.

 This is due to the simplicity of WEP. There's no key exchange, challenge
 response, nothing. Just program the key and see if you can communicate
 with someone that you expect to be on the other end.

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