Hacker News Reader

What I find quite strange is why no Android device seems to use a dedicated hardware encryption module to reduce overhead like iPhones have had since the 3GS. Even security-focused devices like the Blackphone are crippled by the lack of crypto acceleration (http://arstechnica.com/gadgets/2015/09/paranoid-android-redu...). In comparison, iDevices are screaming fast even when fully encrypted (take a look at the storage numbers here http://www.anandtech.com/show/9686/the-apple-iphone-6s-and-i...).

Is there a source to confirm iPhone is equipped with HSM? One theory is the low-end devices want to reduce cost, and furthermore, Android devices are manufactured and sold by more than one company. But you can argue the weakest will eventually participate or die.

There are more details on the HSM in the iOS security guide here. https://www.apple.com/business/docs/iOS_Security_Guide.pdf

This is HSM on the iPhone itself, or on the cloud side?

The iPhone itself

The phone itself. All of the encryption is done in hardware, not just for performance, but for resistance against physical attacks. The dedicated processor is nothing short of Fort-Knox-like if that paper is to be believed fully.

iOS always include hardware accelerated components for various tasks, for example voice, video encoding are super fast on iOS and super slow on high end androids. Androids traditionally doesn't have any hardware acceleration modules.

Well it was all over the news - the Secure Enclave uses a special chip with a unique encryption key hard burnt into it. It encrypts everything that is encrypted on the iPhone, and uses a different key for each app I believe.

> What I find quite strange is why no Android device seems to use a dedicated hardware encryption module to reduce overhead like iPhones have had since the 3GS.

According to the Android team, it's actually even faster to do it in software, at least with the SoC that the Nexus 5x and Nexus 6p use: http://www.androidpolice.com/2015/09/30/the-nexus-5x-and-6p-...

Comparison: https://browser.primatelabs.com/geekbench3/compare/3839281?b...

I find this argument flawed. Why only now are they are removing encryption when hardware is getting more powerful and storage getting faster(read/writes). As another reader pointed out Amazon tablet hardware as also plenty powerful. Google does not control the Android hardware market so if someone wanted to make a phone using a slow processor which did not support hardware encryption(Qualcomm processors do...no one uses it though) they can but performance would be brutal with encryption on.

Amazon controls everything in their ecosystem. They could make the hardware to go with the software.

It's very possible that this never registered high enough on the list of problems to deal with. It's likely that there are very few kindle fire owners that use the encryption.. which is what they say.

The only reason I agree with you is that, if the hardware is the problem.. then why not just say that?

Then this begs the hypothetical question, 'If even only one person used encryption out of all of the devices sold, is it a feature worth keeping?'

I think most people here would say 'yes'.. but would most average company executives?

I don't like the idea that there is no way to freeze the build to avoid the un-encryption and or the possible bricking of a couple kindles for the few that used it however.

It's one thing to say, we don't support this going forward so if it's something you use get a different device next time. It's another to say, we are disabling or bricking, your choice.

When you're selling devices for $50, margins are tight. It is possible the encryption was slowing down the system so instead of adding HW to deal with it, they just simply turned off the feature.

Any idea what HW is in the cheap Kindle tablet?

According to this blog:

http://www.blog.fictiv.com/posts/50-kindle-fire-teardown

* Samsung KLM8G1GEND-B031 - data storage chip

* Mediatek ARM Mt8127A - SoC (system on chip)

* Mediatek MT6323LGA - integrated circuit

I like your analysis until you start to posit that you don't necessarily need to secure information on a book reader. Since you can browse the web and the book reader is a pretty full featured computer there may be banking information or even browsing history that I would want to keep secure or confidential.

> "As an aside, what sort of confidential information are you likely to keep on your book reader, anyway? Or the $50 toy you bought to keep your child quiet during the upcoming road trip?"

Kindle Fire tablets aren't really a 'book reader' any more than an iPad is a 'book reader' (perhaps you're thinking of the eInk versions of the Kindle, such as the Kindle Paperwhite). Kindle Fire tablets can be used for anything a standard tablet would be, so to answer your question... Any web browsing or email content you'd rather not share with the government or hackers.

I was referring to the Kindle readers. But you are correct, the features were removed specifically from the tablets, not the readers. I've edited my post to remove that. Thanks for the correction.

After using encrypted Android devices since 4.0 or so, I find your post a bit misleading. Yes, you do lose performance in benchmarks, but the devices themselves (about 15 or so I've dealt with, mostly branded with Nexus and Samsung brands) did not severely degrade as you're trying to say. They were a bit slower, but not in a way a passerby would notice without actually putting two together.

In my experience, it took about 5 minutes to boot the thing with cyanogen and FDE then the performance was more or less negligible on a nexus5.

I think there may be different factors at play. First of all, the availability of hardware instructions for encryption primitives. Secondly, some flash controllers compress data before it is stored in NAND cells, to reduce write amplification and to improve read/write throughput. Since encrypted data is high-entropy, it does not compress well. Performance takes quite a dive on such controllers.

That said, I used FDE on my Moto X 2014 with Lollipop and it worked without any problems or noticeable slowdowns. But typically Kindle has far more low-end hardware.

>they had to back off of the recommendation because full-disk encryption made the devices run like crap.

This isn't true of all android, just the N6 which was having issues with not having hardware acceleration enabled.

If OEMs want fast crypto they have to do what everyone else does: use methods that work with hardware acceleration and put that hardware in the devices.

There was an update, I believe lollipop 5.1 for the Nexus 6 that improved the performance drastically.

"Apparently, Google has not merged the various drivers that optimize Qualcomm's QCE module for encryption and decryption into AOSP. The generally-assumed reason is that this code is proprietary. Without these optimizations, the Nexus 6's hardware decryption module on the Snapdragon 805 is essentially hamstrung."

http://www.androidpolice.com/2014/11/20/anandtech-posts-side...

I believe the 5.1 update fixed the QCE issue.

This is odd. I had FDE enabled for quite some time on my old Nexus 4 (and now on a OnePlus One) and I've not experienced any performance degradation after I turned it on.

Maybe I was lucky and both phones support hardware acceleration for the relevant crypto primitives.

I would disagree with your theory. Encryption was removed because Amazon discovered virtually no one was using it and the costs associated with supporting it wasn't worth the cost.

Why not both?

Everything's black and white, there's no way multiple things could be factored into a decision.

Yes, it was done for performance! This was obvious once you look at the tablet offerings Amazon has now, none of which are designed for anything more than consumption.

/b

The tablet offerings they have now? Their tablets have never been designed to be anything other than an Amazon store client, which I wouldn't mind too much if the Amazon app store weren't such a wasteland.

I got one for the sole purpose of access to the amazon instance library for my daughter since it wasn't an android offering at the moment.

I tried to use it as an android tablet, I was able to come up with most of the apps needed but in the end it was little things like lack of configuration that just made it useless to me. Not being able to change the keyboard and such.

Now it's only used by my daughter for content and solarium mobile.

I have a 2014 Kindle Fire HDX with FDE enabled, and the performance is fine.