this post was submitted on 15 May 2024
513 points (97.4% liked)
Technology
59466 readers
4132 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I appreciate this thread's nuanced discussion of how file deletion works from a technical standpoint depending on storage medium. But as a user, when I delete something, it should go away forever. I don't care how.
If every time an OS had to delete something it had to fill the space with zeros or garbage data multiple times just to make extra sure it's gone, we'd all be trashing our flash chips very fast, and performance would be heavily degraded. There really isn't a way around this.
The solution to keep private files private is to put them into an encrypted container of some sort where you control the keys.
Well, the storage device should handle that then. And modern NVMEs do. Self-encrypted drives are used to hide deleted information from an attacker that desolders the storage chips.
Edit: there are NVMEs that dont use self encryption, BUT they should still recognize a deleted sector.
That would apply in my "encrypted container of some sort" solution, yes.