B2G/Architecture/System Security: Difference between revisions

B2G/Architecture/System Security (view source)

756 bytes added , 1 November 2012

→‎Proposed Implementation: additional information for split encryption/unlock codes

Confirmed users

502

edits

@@ Line 210: / Line 210: @@
 ** Devices are installed with the bootloader locked by default
 * A user interface must be present to set the encryption password
-* May allow a weaker screen lock password if the user is informed of the possible consequences:
+* Allow a weaker screen lock password:
-** Unlocking the phone screen can give access to sensitive data, depending on the applications and the configuration
+** Problem solved
+*** Unlocking the phone screen is done several times a day, sometimes several times within a few minutes, thus users very rarely use a strong phone unlocking mechanism (generally, a 4 to 8 number PIN code)
+*** User is not tempted to use a weak PIN to decrypt the phone, since decryption only occurs during phone startup (key is kept in memory afterwards)
+** Additional risks
+*** Weaker screen unlock mechanism (such as a PIN), can lead to access to the encrypted data
+** Rationale
+*** It is currently harder to crack a PIN on a running device (no brute force input available)
+*** Shutting the phone down ensures a better level of security assurance since the encryption is using a strong password
+*** Using a PIN for encryption generally renders the encryption useless as those can be cracked in seconds (see for example https://viaforensics.com/viaextract/viaextract-includes-android-encryption-cracking.html )
 == Address Space Layout Randomization (ASLR) ==