Google has a long - hold ambition to make full - magnetic disk encryption mandatory on Android . It did n’t quite work for Lollipop — so it ’s taking another stab with Marshmallow .
With Android 5.0 , attempts to roll out all - encompassing encoding fall through because many devices lack the specs to make it fall out . That led Google to simply ‘ strongly advocate ’ full - disk encryption to phone manufacturers rather than make it obligatory .
Now it ’s changed tack , as IT World describe . In its latestCompatibility Definition for manufacturers , it ’s delineate some new principle about encryption on handsets .
If a handset doest not declare itself as a low - memory gimmick — which signify 512 MB of RAM or less — and it supports a safe lock CRT screen , it must also affirm full - disk encryption . And if the machine has what ’s experience as Advanced Encryption Standard ( AES ) cryptological mathematical operation performance of over 50MB / s , the encoding feature article must switch on by default when the telephone is first set up .
Elsewhere , the same text file also describes other ruler for encryption on Android — demanding encryption uses 128 - bit paint , along with insisting that the encoding key is never written to storage or transmitted off the machine . All very sensitive , though it will do little to cheer U.S. authorities , that already take umbrage at Apple and Google ’s erotic love of encryption .
[ Android Compatibility DefinitionviaIT World ]
Image byScott Akermanunder Creative Commons permit
AndroidEncryptionGoogleSecurity
Daily Newsletter
Get the safe tech , science , and acculturation news program in your inbox day by day .
News from the future , deliver to your present .
You May Also Like
