3 ms·
"Devices that ship with Android 5.0 are encrypted out of the box. If you set a lock screen, you're given the option to require a security challenge before the d
by e12e 12y ago
"Devices that ship with Android 5.0 are encrypted out of the box. If you set a lock screen, you're given the option to require a security challenge before the device turns on. Enable this and a PIN, pattern, or password prompt will come up even before the boot animation. After you pass authentication, the device decrypts the data partition and mounts it, allowing the device to fully boot."
Good news. Not sure if I think it is good news that you can pair the (presumably ok) encryption with face-unlock... though. Seems like it's not possible to (easily) brute force a disk-image off-line any more at least:
http://blog.kaspersky.com/full-disk-encryption-android-5/ http://blog.kaspersky.com/full-disk-encryption-android-5/
“In addition to enabling FDE out of the box, Android L is expected to include hardware protection for disk encryption keys, as well as hardware acceleration for encrypted disk access,” Elenkov concludes. “These two features should make FDE on Android both more secure and much faster.”
Now we'll just have to wait for the source code, to see if this will be usable by all "tenants" on Android hardware... I hope so -- I'd love to be able to drop to a simpler unlock key, knowing that it's eg: set to self-destruct/severely rate-limit after N tries.
- SloopJon 12y agoIn 4.x, the decryption password is the same as the unlock PIN. I'm hoping it's possible in 5.x to separate the two, so that the password can be stronger than the PIN.
- AlyssaRowan 12y agoIt actually never had to be; if you're rooted you can set it fr the command line. http://niki.hammler.net/wiki/Android_Device_Encryption http://niki.hammler.net/wiki/Android_Device_Encryption However, please note that I have not yet reviewed Android 5.x's FDE.
- e12e 12y agoThank you for that. Right now I'm running stock Samsung rom on my Note 3 (thought I'd wait for cyanogen to mix it up with 5.0 before flashing). But at least then there is another option than what I do now, basically a compromise that combines the worst of both worlds: a password/phrase that is too long to be convenient to type in to unlock, and probably too weak to offer real security, assuming the encryption key is generated via a straightforward derivation (not sure if there is any decent stretching involved?). Either way, for a device like a phone, I'm pretty sure TPM is the way to go. Alternatively a strong pass-phrase to unlock/boot, and a hard limit on attempts to unlock the lock screen before the device turns itself off (or at least "guarantees" that the disk is unmounted and the key wiped from ram...).