Vincent96 Secure Erase like raccoondad said to destroy data permanently.
schweizer secure delete some SSDs
We cannot run these commands on our phone.
I wrote about why this method isn't 100% safe:
Johnnyloans 1) ATA secure erase / nvme sanitize
Broken in most NAND controllers that storage manufacturers purchase.
"Even vendor-provided “secure erase” commands (e.g., ATA SECURITY ERASE UNIT) may not guarantee full physical sanitization: in 68% of tested NVMe drives (2023 NIST IR 8457 lab validation), residual data persisted"
-https://lifetips.alibaba.com/tech-efficiency/secure-erase-methods-probably-wont-work-on-your-solid-s
68% failure rate is unsafe to trust alone. GOS doesn't use this anyway to the best of my knowledge.
The command typically does more than deleting keys. I can't speak on all controllers.
Erasing keys is enough for 99.9999% of people, however:
https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later
You'll notice my original reply is to raccoondad, who should know better by now, but his name is captain Ahab as it turns out.
schweizer The method of overwriting sector by sector with zeros and/or random data like we did in the days of magnetic hard disks is obsolete with SSDs.
I have an entire explanation on this:
Johnnyloans Overwrite the entire drive
Let's give a generous 10% over-provision. I completely fill the drive and thus--actually--destroy 91% of the data (1/1.1=0.91). I delete files, wear-leveling kicks in, and I fill it again.
raccoondad: "You are mistaking unencrypted HDD wiping concepts like DoD 5220.22-M"
No, I am simply leveraging mathematical truths in our favor.
A U B >= A
(realistically, "=" shouldn't be there)
Layered security right? My approach will surely be safer than simply deleting a key and there’s little to sacrifice--no harm done.
If you have a method for retrieving data that's been overwritten, please apply for a patent at your earliest convenience.