Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by jjeaff on Monday August 09, 2021 @03:51PM
(#28121547)
I don't think an app has the kind of low level access required to actually wipe something from memory. Unless android has an API with a function to do so. I assume you are just telling the OS to delete the file and the OS does that however it normally does that. Truly wiping a file from storage requires overwriting it with random data.
[ Parent
| on HN ]
Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by jaywalk on Monday August 09, 2021 @04:21PM
(#28121875)
That doesn't seem to be the case here, because the files are actually deleted once the user logs out of Snapchat. So it's obviously the Snapchat app itself that is triggering the file deletion, not the OS.
Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by pessimizer on Monday August 09, 2021 @05:00PM
(#28122281)
The person you're replying to is referring to making the files unrecoverable. The word most often used is "shred."
edit: The Snapchat app, like the vast majority of applications, asks the OS to delete files. It very probably doesn't have any direct access to I/O.
Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by treesknees on Wednesday August 11, 2021 @10:19AM
(#28142290)
Seems like an API that the OS should expose. I'm sure other apps like banking/financial would benefit from this, too.
Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by fragmede on Monday August 09, 2021 @04:17PM
(#28121826)
With wear leveling and modern filesystems, it's harder than that actually overwrite the file on disk (for modern definitions of the word disk). The operating system will ask the storage device to delete the data, but there aren't actually guarantees that the storage device actually listened to the operating system's request to delete the data.
Re:Snaprecovery: Recover old Snaps that have “disappeared” f...
by m4rtink on Monday August 09, 2021 @06:03PM
(#28122882)
Which is why if you care about sensitive data not being recoverable from failed media (eq. banking database, PII, mediacal records, etc.) you should always use full disk encryption (LUKS, bitkeeper, veracrypt, etc.).
That way anything one could recover from that device afterwards would be effectively random noise to them without the decryption key, regardless how the firmware of the device actually wrote the individual data blocks.