Flutterby™! : So is Google going to get the FBI to

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

So is Google going to get the FBI to

2016-02-28 04:15:07.704474+00 by Dan Lyke 3 comments

So is Google going to get the FBI to demand a back door for Android, or just going to cede the privacy geek market to Apple?

[ related topics: Apple Computer Privacy Law Enforcement Economics ]

comments in ascending chronological order (reverse):

#Comment Re: So is Google going to get the FBI to made: 2016-02-28 16:00:07.095937+00 by: Jack William Bell

You are assuming the FBI doesn't ALREADY have a back door for Android.

Mind you, I'm assuming the government ALREADY has a back door for iOS too. They are just being coy about it.

#Comment Re: So is Google going to get the FBI to made: 2016-02-29 16:15:58.249123+00 by: Dan Lyke

Oh, I totally assume that the Android devices are less secure against physical possession attacks than the iOS devices. But Apple is getting a lot of positive publicity in being the company that's willing to protect privacy against FBI overreach, and Google hasn't jumped on that wagon yet.

#Comment Re: So is Google going to get the FBI to made: 2016-03-01 10:33:02.501514+00 by: DaveP [edit history]

Saw an article yesterday that only 6% or so of Android devices have whole-disk encryption on by default, due to slow uptake of new software versions because phone companies suck. 94% of iPhones have encryption on, since Apple makes it pretty easy to upgrade to the latest software.

This article isn't the article I read, but has some of the details.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.