New
#40
Well, here's a common example. After using Firefox on my boot HDD for an hour, using Recuva I can get a few hundred images and documents that were written to FF's cache that FF allegedly "deleted" when it was shut down. Oops. Using Recuva to multi-pass erase those items wipes them clean. I can't do that on a SSD.
I'm aware of the Secure Erase utility for the entire drive that's used on SSDs. I am interested in multiple-pass erasing free space and chosen files and folders only. Say some undesirable entity enters my home - a criminal, the government (ahem) - and gets their hands on my hard drive. Unless I multipass erase empty space or deleted files on my HDD, they're retrieveable. This can't be done on a SSD. To me, that's a huge security dealbreaker.
I did read at least two articles saying that completely encrypting a SSD causes trouble with TRIM because there are no "empty" blocks of memory to work with... TRIM sees the entire drive as filled to the brim with data. If or when I can find the articles again, I'll gladly post the link(s).
I do realize that most people don't think of this, don't really care, think they have nothing to hide, and that I seem to be the only one bleating about it. That's fine.