Created attachment 8438993 [details] VID_20140612_145944.3gp [1.Description]: Input wrong lockscreen password for 10 times, then the password edit box will respond more slower. Attachment video:[VID_20140612_145944.3gp] Attachment log:[bugreport.txt]&[logcat.txt] Happened time: 6:22 AM [2.Testing Steps]: Precondtion: Set a lockscreen password 1. Lock screen and light up screen 2. Input wrong password 3. Repeat step 2 for 10 times [3.Expected Result]: 3. When user input wrong password, these password in edit box should be cleared quickly. [4.Actual Result]: 3. These wrong password in edit box will not be cleared immeditely from the 7nd time, and its reaction is getting slower with wrong input count increasing [5.Reproduction build]: Gaia 7709936aeb21859d1607dbd038489493803bb085 Gecko https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/5bf038fae0f1 BuildID 20140522160202 Version 30.0 [6.Reproduction Frequency]: Always Recurrence,3/3
Priority: -- → P5
Whiteboard: bamboo → bamboo[c=effect p= s= u=]
Product Team, 10 failed lockscreen attempts seems excessive, do we have any feature planned to limit the number of failed attempts before locking the phone or temporarily disabling further attempts? FxOS Perf Triage
Whiteboard: bamboo[c=effect p= s= u=] → [c=effect p= s= u=] bamboo
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bruce(In reply to Mike Lee [:mlee] from comment #3) > Product Team, > > 10 failed lockscreen attempts seems excessive, do we have any feature > planned to limit the number of failed attempts before locking the phone or > temporarily disabling further attempts? Bruce?
Flags: needinfo?(ffos-product) → needinfo?(bhuang)
After 5 attempts, each failed input causes the wait time to exponentially increase in order to dissuade brute force attempts. That's why it starts to feel sluggish at around 8~10 tries.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
Whiteboard: [c=effect p= s= u=] bamboo → [c=effect p= s=2014.08.15.t u=] bamboo
You need to log in before you can comment on or make changes to this bug.