3 ms·

I'm surprised people actually think TRIMming is in any way a "secure delete" operation. It's basically the "quick format" of SSDs: "hey, all those blocks here,

I'm surprised people actually think TRIMming is in any way a "secure delete" operation. It's basically the "quick format" of SSDs: "hey, all those blocks here, I don't care about them anymore, use them as if they were free..." Without OS-side encryption, Secure Erase is the only reliable option (SSD encrypts everything with an internal key which then gets deleted by the secure erase command, leaving only random data behind)

marcosdumay 4y ago
> It's basically the "quick format" of SSDs: "hey, all those blocks here, I don't care about them anymore, use them as if they were free..." Due to implementation details, SSDs can only use a block if it is clear. Thus trimming a block and waiting for long enough would be sufficient to erase the data if the driver actually enforced that the block will be reused. So, it's not good enough, but this is not obvious at all.
- pkaye 4y ago
  But there is a logical to physical mapping table so that data might be spread across multiple physical blocks.