Google relaxes Android 5.0 Lollipop’s encryption requirements

BY

Published 2 Mar 2015

NSFW AI Why trust Greenbot

We maintain a strict editorial policy dedicated to factual accuracy, relevance, and impartiality. Our content is written and edited by top industry professionals with first-hand experience. The content undergoes thorough review by experienced editors to guarantee and adherence to the highest standards of reporting and publishing.

Disclosure

Android 5.0 Lollipop

One of the security steps within Android 5.0 Lollipop is full-disk encryption, which kicks into gear the first time a device is booted up.

However, that’s changing moving forward, as Google is reportedly slackening some of those requirements for Android manufacturers, according to a report published by Ars Technica. Based on findings within an Android Compatibility Definition document (PDF), Android 5.0-based devices must support the ability for full-disk encryption, but it’s not required to be activated. If it is, though, which Google says is “very strongly recommended,” it must be activated the first time the device gets switched on.

Google also states that these rules could change, and soon, so it says that manufacturers should just activate the security feature now.

9.9 Full-Disk Encryption

If the device implementation has a lock screen, the device MUST support full-disk encryption of the application private data (/data patition) as well as the SD card partition if it is a permanent, non-removable part of the device. For devices supporting full-disk encryption, the full-disk encryption SHOULD be enabled all the time after the user has completed the out-of-box experience. While this requirement is stated as SHOULD for this version of the Android platform, it is very strongly RECOMMENDED as we expect this to change to MUST in the future versions of Android.“

It’s believed that Google made this decision so that manufacturers could have more time to determine that their devices function correctly with the full-disk encryption activated. It’s known that many Nexus 6 owners have reported some performance issues with the feature, so this could be a means to see that doesn’t happen again.

[via Ars Technica]