#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 greenfeld):

 Replying to [comment:1 dsd]:
 > Maybe you'll still argue that the behaviour is wrong, but this is at
 least a little bit debatable.

 This bug/issue is not about WEP not knowing when to do quit necessarily;
 it's more the GUI saving a value when the "OK" button is grayed out and
 the key entered does not match one of the two allowed formats (a
 hexdecimal number of one of two lengths) and is therefore invalid.  The
 GUI normally does seem to enforce both the allowed data and lengths when
 "Hex (40/128 bits)" is selected as the WEP key type by disabling the "OK"
 button for invalid inputs.


 And Network Manager at least in Fedora 14 knows immediately that "Hello"
 is not a valid WEP key, logging "NetworkManager[pid]: <warn> Invalid WEP
 key 'wep_key0'" to /var/log/messages, and then going on to the next
 connection.  I do not see this behavior in 10.1.2, so perhaps we will need
 to do some testing in this area to see if something breaks as we move
 forward.

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