Closed
Bug 1177373
Opened 10 years ago
Closed 10 years ago
lock passcode not requested when powering up
Categories
(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)
Firefox OS Graveyard
Gaia::System::Lockscreen
Tracking
(b2g-v2.2 unaffected, b2g-master affected)
RESOLVED
DUPLICATE
of bug 1173284
| Tracking | Status | |
|---|---|---|
| b2g-v2.2 | --- | unaffected |
| b2g-master | --- | affected |
People
(Reporter: jya, Unassigned)
Details
(Keywords: dogfood, regression, sec-high, Whiteboard: [bzlite])
User-Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Phone battery was flat and phone turned off. After charging and restarting it, I wasn't prompted for my password when I unlocked the screen.
So anyone can access the phone, even if passcode is enabled
Note: if you reboot the phone, the passcode should appear as per expected.
QA Wanted : please check flame : flash phone, set passcode, turn off and turn on, unlock and see.
This might be a dup of bug 1173284?
Keywords: qawanted
| Reporter | ||
Comment 2•10 years ago
|
||
not sure if it's an important detail or not. But I didn't voluntarily turn off the phone. It turned off by itself after it ran out of battery
| Reporter | ||
Comment 3•10 years ago
|
||
Ok, I can reproduce it by simply turning off the phone and then back on.
Comment 4•10 years ago
|
||
I was able to reproduce this issue on Flame 3.0. Repro rate is 5/5. Note that as soon as phone restarts, you have to unlock it before it falls asleep again; the passcode screen will appear if the screen had been turned off either manually or by timing out after rebooting.
Device: Flame (full flashed, 319MB, KK)
BuildID: 20150626010205
Gaia: 038e917076271d304b906a41b4de670e505c67ae
Gecko: bbc26cc168c7
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0 Master)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
-------
This issue does NOT reproduce on Flame 2.2. Rebooting phone and immediately unlocking it shows the passcode screen. Bug repro rate: 0/3.
Device: Flame (full flashed, 319MB, KK)
BuildID: 20150626002504
Gaia: 1f8981d7872e3c0053571c26fb3edaf401844d75
Gecko: 2f8b845e5fa3
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → unaffected
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Keywords: qawanted → regression
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Updated•10 years ago
|
Keywords: sec-critical → sec-high
Updated•9 years ago
|
Group: b2g-core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•