Closed
Bug 833614
Opened 13 years ago
Closed 12 years ago
[tethering] WPA minimum password length should be enforced in wi-fi tethering settings
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:tef+, b2g18+)
RESOLVED
DUPLICATE
of bug 818829
blocking-b2g | tef+ |
Tracking | Status | |
---|---|---|
b2g18 | + | --- |
People
(Reporter: MattN, Assigned: arthurcc)
References
()
Details
STR:
1) Go to Settings > Internet Sharing
2) Turn off Wi-fi hotspot if it is on
3) Tap "Hotspot settings" button
4) Choose Security: WPA2 (AES) or WPA (WKIP)
5) Set password to a value with less than 8 characters
6) Tap OK
7) Turn Wi-Fi hotspot on
8) Try to connect to the hotspot from another device (Device B) which enforces a 8 character minimum ASCII password length for WPA/WPA2 (e.g. OS X 10.7).
Actual result:
Device B will not accept a password less than 8 ASCII characters. User is confused because they typed the password which matches the one shown in Gaia. User thinks the tethering feature is broken.
Expected result:
Wi-fi hotspot settings should be validated in step 6 when OK is pressed (and while typing the password if the security field is moved to the top of the settings). A password shorter than 8 ASCII characters should not be accepted when WPA/WPA2 is security is selected.
The hotspot settings should also be validated when the wi-fi hotspot is turned on in case the existing password is too short. Taking the user to the hotspot settings page with the validation error would probably be suitable. The password requirements should probably be enforced in wi-fi code.
There is some discussion about where the 8 comes from at http://serverfault.com/a/165102
"…the IEEE standard states in H.4 Suggested pass-phrase-to-PSK mapping (which includes a discussion of security considerations):
A pass-phrase is a sequence of between 8 and 63 ASCII-encoded characters.
The limit of 63 comes from the desire to distinguish between a pass-phrase
and a PSK displayed as 64 hexadecimal characters."
I don't know how widespread the client enforcement of this password length is.
Updated•12 years ago
|
tracking-b2g18:
--- → ?
Updated•12 years ago
|
Comment 2•12 years ago
|
||
Vincent, this bug is important for a partner. Can you or someone else fit it into your existing queue?
Assignee: nobody → vchang
Flags: needinfo?(vchang)
Comment 3•12 years ago
|
||
According to STR step 5, Set password to a value with less than 8 characters
We should limit the password length in gaia. Evelyn, can you help to take this ?
Flags: needinfo?(vchang) → needinfo?(ehung)
Updated•12 years ago
|
Assignee: vchang → ehung
Comment 4•12 years ago
|
||
Redirect this to Arthur, because I'm working on other issues.
Assignee: ehung → arthur.chen
Flags: needinfo?(ehung)
Updated•12 years ago
|
blocking-b2g: --- → tef?
Comment 5•12 years ago
|
||
qawanted to check if this issue can be reproduced in v1.0.1, if so, we should block on it.
blocking-b2g: tef? → tef+
Keywords: qawanted
This reproduces on v1.0.1
Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/bc2b669a4e27
Gaia 1a6e1cd7715a5192b32db4b7127c5ae5b8162a7a
BuildID 20130311230203
Version 18.0
WPA and WPA/2 have min password lengths. Doing these does not meet that requirement.
Keywords: qawanted
Comment 7•12 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #6)
> This reproduces on v1.0.1
> Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/bc2b669a4e27
> Gaia 1a6e1cd7715a5192b32db4b7127c5ae5b8162a7a
> BuildID 20130311230203
> Version 18.0
>
> WPA and WPA/2 have min password lengths. Doing these does not meet that
> requirement.
What OS was this verified on - every device is impacted? Can we make #8 of the above STR more explicit?
Assignee | ||
Comment 8•12 years ago
|
||
This bug has been fixed in master with the patch of bug 818829. https://github.com/mozilla-b2g/gaia/commit/22f5874ffefdcfcfeb6217ed0be83da80352858e
Suggest to uplift this patch to corresponding branches.
Comment 9•12 years ago
|
||
Mark as dup of 818829 and correct the flags. We should uplift the fix there.
Status: NEW → RESOLVED
Closed: 12 years ago
status-b2g18:
affected → ---
status-b2g18-v1.0.1:
affected → ---
status-firefox22:
fixed → ---
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•