Issue metadata
Sign in to add a comment
|
Invalid length passphrase handling for WEP network not working as expected. |
||||||||||||||||||||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 65.0.3325.9> Chrome OS Version: <From about:version: Platform 10323.1.0> Chrome OS Platform: <Coral> <b>Network info: <network, encryption type, router model (if known)></b> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: WEP 1) Attempt to connect to a WEP network 2) Provide an invalid passphrase of lengths 0, 1, 7, 9, 12, 25, 27, 30 characters Expected Result: It should not try connecting when configuring network fails. Actual Result: UI displays "Error configuring network" error but 1) continues to connect to the WEP network. 2) wifi icon goes into connecting (oscillating/scanning) mode. Also noted: The connect button does not get enabled after entering the minimum 5 characters (For WEP and WPA networks). Feedback report link for logs and screenshot. https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=aashu&lReport=84969687504
,
Jan 24 2018
This is a different issue specifically for WEP network. I added "connect" thing as a side-note. @stevenjb Can you re-look the issue?
,
Jan 24 2018
,
Jan 25 2018
,
Jan 31 2018
I do not see anywhere in the old Chrome code that tests anything other than that the min PSK or WEP passphrase length >= 5. However, Shill fails immediately with an invalid WEP passphrase length. That was not being handled correctly for a while but should be handled correctly now in ToT and in the next 65 rev (>= 65.0.3325.39). i.e. Shill will fail immediately and 'Bad password' will be displayed in the config dialog. I'll mark this fixed but not mark it as a duplicate so that we can verify it independently, however no additional merge will be required.
,
Jan 31 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-65; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-65 label, otherwise remove Merge-TBD label. Thanks.
,
Jan 31 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by steve...@chromium.org
, Jan 23 2018Status: Duplicate (was: Untriaged)