iPhone 3.0 OS Bug Reveals Deleted E-Mail

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Engadget is reporting that a bug in the iPhone 3.0 OS allows deleted e-mail to be retrieved and viewed. As long as you know the subject line, you can pull up months-old deleted e-mail in Spotlight. I predict that this will not be good for some peoples’ relationships.

We're not sure when the search cache finally deletes emails, but it doesn't appear to happen quickly: Matt Janssen, who discovered the bug, says he's been able to pull up emails three or four months old
 
The email is never delted, it's stored by Apple forevar. Invading your privacy the best since 2006!
 
Someone, somewhere, at sometime will create an OS or a program that when you hit delete, it really means delete. Not have it hang around in some digital ether waiting for a forensics team or a bug to come back and resurrect it.
 
Someone, somewhere, at sometime will create an OS or a program that when you hit delete, it really means delete. Not have it hang around in some digital ether waiting for a forensics team or a bug to come back and resurrect it.

You have to pay a severe performance penalty for that. You will basically have to write over the deleted file in the hard drive instead of just deleting it. Current delete method works fine most of the time. They should just add a "secure delete" or something that will overwrite the data after you delete it.
 
After this, and the iPhone's secret taking pictures of your home screen, i'm wary of it and the potential for spying...
 
You have to pay a severe performance penalty for that. You will basically have to write over the deleted file in the hard drive instead of just deleting it. Current delete method works fine most of the time. They should just add a "secure delete" or something that will overwrite the data after you delete it.

So? What percentage of the time is the memory being written at 100% capacity? .1%? Just have a simple queue to erase deleted files while the controller is idle. You sure don't need your phone performing at maximum capacity when it's sitting in your pocket.
 
So? What percentage of the time is the memory being written at 100% capacity? .1%? Just have a simple queue to erase deleted files while the controller is idle. You sure don't need your phone performing at maximum capacity when it's sitting in your pocket.

I was referencing computers. I don't really know about the iPhone(not gay). However, I'd imagine doing a full delete on everything would still cause problems though. It's more expensive and needless. You'd still need to pick what gets a full delete and what gets your standard delete.
 
I was referencing computers. I don't really know about the iPhone(not gay). However, I'd imagine doing a full delete on everything would still cause problems though. It's more expensive and needless. You'd still need to pick what gets a full delete and what gets your standard delete.

Expensive in what sense? If you really want to be picky you have have the queued over-writes happen when it is charging.
 
You have to pay a severe performance penalty for that. You will basically have to write over the deleted file in the hard drive instead of just deleting it. Current delete method works fine most of the time. They should just add a "secure delete" or something that will overwrite the data after you delete it.

Having that as an option would be cool. Like secure delete marks a file to be overwritten first chance it gets, instead of normal delete where it just marks it for deletion. This would be cool across all OS'es and mobile devices. Maybe an extra option would be for it to do the active overwriting while its charging.
 
Expensive in what sense? If you really want to be picky you have have the queued over-writes happen when it is charging.

You could. But that's a little different as that gives a delay to file deletion. Point being: doing this doesn't have any real advantages.

Having that as an option would be cool. Like secure delete marks a file to be overwritten first chance it gets, instead of normal delete where it just marks it for deletion. This would be cool across all OS'es and mobile devices. Maybe an extra option would be for it to do the active overwriting while its charging.

No, A secure delete will find where the file is written and write garbage data to destroy the file. If you want something really gone, delayed deletes are not acceptable.
 
well me and my brother just got new Iphones, and you can just do what he did, password lock the darn phone.

I don't (then again my phone is rarely not on my person), but then again there is probably equivicably incriminating stuff in those wonderful text "threads" that index the full text history for any given person in neat little packages (that I would be far too lazy to "trim").
 
by incriminating and the like I am referring to the relationship comment in the original article :)
 
Back
Top