After Backlash, Amazon Promises To Bring Back Encryption On Fire OS

from the of-course dept

Just to close the loop on this one: just after the firestorm last week when Amazon was called out for removing device encryption from Fire OS 5 (at the very same time as its CTO was saying encryption is "mandatory" and the company signed on to a brief supporting Apple in the encryption fight, the company has admitted that it will restore encryption to Fire OS 5 "sometime in the spring."

The company had insisted that no one was really using it -- and some suggested that there may have been performance issues when encryption was turned on. But, even if that's the case, it still makes little sense to have yanked the feature entirely. For the small number of people who were using it, it was clearly an important feature. And, given all of this, it's no surprise Amazon is bringing it back. It still doesn't quite explain why they removed it in the first place, but it's good to see that this got settled in the proper way in the end.
Hide this

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

Filed Under: backlash, encryption, fire os
Companies: amazon


Reader Comments

Subscribe: RSS

View by: Thread


  1. identicon
    Anonymous Coward, 7 Mar 2016 @ 4:11pm

    Actually I don't believe it got settled at all; at least not from my perspective. I own a Kindle Fire. What it will not be doing is connecting to the internet. Not to receive the latest downgrade nor the promised but as of yet vaporware return.

    Amazon would not be the first company to promise to bring something back by popular acclaim and when the time comes fail to do so.

    What Amazon has shown me is it's willingness to yank back what was sold on it's devices. That particular device for all their claims of licensing was not rented; it was purchased for ownership. As such Amazon doesn't get to do whatever in the hell it wants with my device without my permission. The connection here is that if it is not allowed to connect to the internet it will not receive upgrades. That isn't a good thing. Neither will it receive downgrades.

    I purchased the device new. I purchased it with the items on it over others because of the choices available to me with it. Yanking back those choices after the sale does not sit well with me and I don't have to agree with it.

    What Amazon has shown in this little escapade, is that it is yet another corporation that can not be trusted not to alter it's deal after the sale. So Amazon will not recieve datamining back, nor will it be able to downgrade the device from it's present configuration without my approval. I don't approve of this freebee downgrade at all.

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here



Subscribe to the Techdirt Daily newsletter




Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat

Warning: include(/home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/rc_promo_discord_chat.inc): failed to open stream: No such file or directory in /home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/rc_module_promo.inc on line 8

Warning: include(): Failed opening '/home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/rc_promo_discord_chat.inc' for inclusion (include_path='.:/usr/share/pear:/home/beta6/deploy/itasca_20201215-3691-c395:/home/beta6/deploy/itasca_20201215-3691-c395/..') in /home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/rc_module_promo.inc on line 8
Recent Stories
.

This site, like most other sites on the web, uses cookies. For more information, see our privacy policy. Got it
Close

Email This

This feature is only available to registered users. Register or sign in to use it.