Project

General

Profile

Actions

Issue #1854

open
JR

Device not rebooting after 5 unsuccessful unlock attempts

Issue #1854: Device not rebooting after 5 unsuccessful unlock attempts

Added by Jeremy Rand almost 9 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Security
Target version:
Start date:
12/19/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 3 (I9300)
Grant:
Type of work:
Communication (mails, contacting people, etc), Unknown

Description

https://redmine.replicant.us/projects/replicant/wiki/UsageNotes states:

If a separate encryption password is in place and a PIN or password is set for the lockscreen, another security measure is active: After five unsuccessful attempts to unlock the screen, the device is rebooted and the attacker is faced with the much stronger encryption passphrase. This makes brute-force attacks on the lockscreen much harder.

This doesn't seem to work for me. I have an encryption password, and a different lockscreen password, and I've entered the wrong password 7 times in a row, and the device doesn't reboot.

This is with Replicant 6.0 0003.

AD Updated by Andrés D about 8 years ago Actions #1

This works for me with 6.0 0004 nightly builds by Asara. After 5 wrong unlock attempts it reboots, I tried with both password and pin as unlocking methods.

JK Updated by Joonas Kylmälä almost 8 years ago Actions #2

I cannot reproduce the issue on 6.0 0003. Well... I can but the reason is https://git.replicant.us/replicant/frameworks_base/tree/packages/Keyguard/src/com/android/keyguard/KeyguardAbsKeyInputView.java#n45. So basically the Keyguard code doesn't care about passcodes that are shorter than 3 characters and you can type those infinite amount of times. Jeremy, could it be that the passcodes you tried were 3 or less characters?

_R Updated by _I3^ RELATIVISM over 5 years ago Actions #3

  • Type of work Communication (mails, contacting people, etc), Unknown added
Actions

Also available in: PDF Atom