Slashdot Mirror


Apple Updating iOS To Address Privacy Concerns

wiredmikey writes "[Apple] said that over the next few weeks it would release a software update for iOS that would reduce the size of the crowd-sourced Wi-Fi hotspot and cell tower database cached on the iPhone, cease backing up the cache, and delete the cache entirely when Location Services is turned off. Additionally, Apple said that in the next major iOS software release the cache would be encrypted on the iPhone, though a timeline for that was not provided."

4 of 318 comments (clear)

  1. Re:Bug? by mangino · · Score: 5, Insightful

    Almost all bugs would be caught by a single testcase if you thought about writing it. Most often the problem is that nobody concerned the scenario and though to write a testcase. While it could be mailicious, it could also be just an accident.

    --
    Mike Mangino
    mmangino@acm.org
  2. Re:Good...? by SvnLyrBrto · · Score: 5, Insightful

    How do you suppose the phone company knows what cell you're in, so they can route calls to your phone? How do you suppose they get their E911 data?

    As long as you have the thing powered on, the phone company know where you are. And if the police want to know, they won't go to your house, hack your computer, and read the log backup. They'll just go to the phone company with a subpoena.

    This whole controversy was much ado about nothing. The only thing that was different was that the user had access to the data that "the man" had all along.

    --
    Imagine all the people...
  3. Re:nice by jessecurry · · Score: 5, Insightful

    Apple: We didn't see anything wrong with the previous implementation, but it seems that our customers do. We'll take steps to make sure that our implementation is in-line with what our customers desire.

    --
    Those who know, do not speak. Those who speak, do not know. ~Lao Tzu
  4. Re:Bug? by Anonymous Coward · · Score: 5, Insightful

    Not if the bug is in the requirements. You can't test for something if there is no requirement for it. One of the biggest failures of how agile/XP methodologies are implemented, they skimp on the requirements documentation.