Apples formal response

http://www.apple.com/pr/library/2011/04/27location_qa.html

-Chris



On Fri, Apr 22, 2011 at 5:05 PM, Chris Penn <cantorm...@gmail.com> wrote:
> "Why and How Apple Is Collecting Your iPhone Location Data"
>
> I wonder, does this solve the problem?
> http://no-geolocation.blogspot.com/2010/08/01-what-is-geolocation.html
>
> Chris...
>
> On Fri, Apr 22, 2011 at 9:13 AM, Chris Louden <ch...@chrislouden.com> wrote:
>>
>> Why and How Apple Is Collecting Your iPhone Location Data
>>
>> http://www.wired.com/gadgetlab/2011/04/apple-iphone-tracking/
>>
>> -Chris
>>
>>
>>
>> On Thu, Apr 21, 2011 at 9:51 AM, David Kaiser <dkai...@cdk.com> wrote:
>> > Thought I'd reply to this previous post of mine.  There is now a story
>> > about iOS tracking your location updates and keeping a permanent
>> > database of this information.  (It is also synced to your computer for
>> > you iTunes users that sync your phone)
>> >
>> > http://www.wired.com/gadgetlab/2011/04/iphone-tracks/
>> > http://www.cnn.com/2011/TECH/mobile/04/20/iphone.tracking/
>> >
>> > Also, the device that the cops in Michigan are carrying doesn't need
>> > your unlock code, it puts your device into flash-mode and just transfers
>> > off the raw files.  Of course, they can decrypt and read these files
>> > like where you have been.
>> >
>> > I'm really seriously thinking we need a true community-driven, open
>> > source phone OS.  There just are not any features which can guarantee my
>> > privacy in any of the current phones.
>> >
>> >
>> >
>> > On 4/19/11 9:34 PM, David Kaiser wrote:
>> >> I saw this article on slashdot, but haven't looked into whether these
>> >> claims are true yet.
>> >>
>> >>
>> >> http://apple.slashdot.org/story/11/04/19/2231240/Michigan-Police-Could-Search-Cell-Phones-During-Traffic-Stops
>> >>
>> >> This sounds like our epic thread of years past about having an
>> >> encrypted
>> >> laptop when you cross the border and whether or not law enforcement has
>> >> the right to invade your digital privacy without cause.  In this case,
>> >> I'm posing the question about what would be the best way to
>> >> design/build/hack a phone which would behave as follows:
>> >>
>> >> -all user storage (phone contacts, calendar items, e-mails) are kept in
>> >> removable storage like microSD
>> >>
>> >> -microSD chip is mounted via a FUSE like system that uses a strong
>> >> crypto, using a strong key (4096bit or so) with a passphrase that the
>> >> user knows (and allows for more than the standard 4-digit "unlock
>> >> code" size)
>> >>
>> >> -at boot-up, the initialization procedure prompts the user for the
>> >> strong
>> >> key passphrase before allowing access to the user storage
>> >>
>> >> then if you happen to be driving through Michigan and a cop signals
>> >> their
>> >> lights to pull you over, you just hold down the power button on your
>> >> phone for 5 seconds, and no matter what crazy device they think can
>> >> crack the typical "unlock codes" to read your files, they wouldn't be
>> >> able to get past your encryption
>> >> _______________________________________________
>> >> LinuxUsers mailing list
>> >> LinuxUsers@socallinux.org
>> >> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>> >
>> > _______________________________________________
>> > LinuxUsers mailing list
>> > LinuxUsers@socallinux.org
>> > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>> >
>> _______________________________________________
>> LinuxUsers mailing list
>> LinuxUsers@socallinux.org
>> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>
>
>
> --
> "As we open our newspapers or watch our television screens, we seem to be
> continually assaulted by the fruits of Mankind's stupidity."
>  -Roger Penrose
>
> _______________________________________________
> LinuxUsers mailing list
> LinuxUsers@socallinux.org
> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>
>
_______________________________________________
LinuxUsers mailing list
LinuxUsers@socallinux.org
http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers

Reply via email to