{"id":26070,"date":"2014-09-19T19:41:09","date_gmt":"2014-09-19T23:41:09","guid":{"rendered":"http:\/\/www.opensource.im\/?p=26070"},"modified":"2014-09-19T19:41:09","modified_gmt":"2014-09-19T23:41:09","slug":"google-android-l-turns-data-encryption-on-by-default","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/google-android-l-turns-data-encryption-on-by-default.php","title":{"rendered":"Google: Android L turns data encryption on by default"},"content":{"rendered":"<p><p>    Turning on data encryption can make a huge difference in case    your Android device is lost or stolen, as it will make it    extremely difficult -- if not impossible -- for a third-party    to access yourfiles. It also gives you quite a bit of    time to remotely wipe your device, which means that your    photos, videos, texts and whatnot have a better chance of    remaining private.  <\/p>\n<p>    And if the local authorities want to take a peek, theyare    also out of luck -- it's good news for those involved in    criminal enterprises, and others as well. All this sounds great    from a privacy and security standpoint, except that encryption    has never been enabled by default in Android. But that is soon    about to change.  <\/p>\n<p>    In a statement that was just given to The Washington Post,    Google spokesperson Niki Christoff revealsthat \"As part of [Google's]    next Android release, encryption will be enabled by default out    of the box, so you won't even have to think about turning it    on\".  <\/p>\n<p>    Google's next Android release is known as \"Android L\" at this    stage, and will be ready for prime time later this year, if the    launch date of past releases is of any indication. Android L    has been made available to beta testers, and features a    redesigned user interface, a new default runtime, extra    security features, 64-bit support and more. You can read about    it here.  <\/p>\n<p>    The encryption key, which is needed to unlock the contents of    the internal storage (and, presumably, the microSD card too),    will continue to be only in your control, as it has been the    case in the past three years, according to Christoff. This is    very similar to how Apple's now doing things with iOS 8, which also    only gives you the encryption key. To take advantage of this, a    passcode must be set up.  <\/p>\n<p>    That last bit is extremely important because encrypting an    Android device without using any sort of passcode is    practically impossible right now, and, frankly, pointless. For    instance, Android 4.4 KitKat requires users to set up a PIN in    order to encrypt the contents of the internal storage and    microSD card.  <\/p>\n<p>    How strong the PIN is will determine how easy it will be for a    third-party to render your encryption efforts useless. Using a    complex sequence is recommended, even though it may make the    unlocking more difficult. That said, I am using an eight-digit    PIN right now and I quickly got used to it.  <\/p>\n<p>    Photo Credits:Slavoljub Pantelic\/Shutterstock  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Excerpt from:<br \/>\n<a target=\"_blank\" href=\"http:\/\/betanews.com\/2014\/09\/19\/google-android-l-turns-data-encryption-on-by-default\" title=\"Google: Android L turns data encryption on by default\">Google: Android L turns data encryption on by default<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Turning on data encryption can make a huge difference in case your Android device is lost or stolen, as it will make it extremely difficult -- if not impossible -- for a third-party to access yourfiles. It also gives you quite a bit of time to remotely wipe your device, which means that your photos, videos, texts and whatnot have a better chance of remaining private. And if the local authorities want to take a peek, theyare also out of luck -- it's good news for those involved in criminal enterprises, and others as well. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-26070","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26070"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=26070"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26070\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=26070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=26070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=26070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}