@izaya now the only audible hint we have from laptops is the fan spinning up when somethings' burning too much cputime...
@izaya I miss the era of drive heads giving away when the nightly cronjobs have started...
because I'm an imperfect human who cannot memorize 128 bits of random data, and uses a password weaker than that.So it may happen that the password will be guessable easier than I thought, or maybe I'll type it in the wrong place and it will be compromised.
Therefore I use LUKS, which uses PBKDF to derive encryption key from password and keyslots. And the keyslots are designed so that they can be easily destroyed when on HDD. But on SSD, you can't reliably destroy the keyslots.
@Wolf480pl That's right, but as @izaya points out, you can never be sure how an HDD erases blocks these days. For instance, it's well known that they have a bunch of hidden spares for when a track starts to have dangerously too many error bits... and once a track has been swapped, there's no way to reach the old copy other than (perhaps) wiping the internal bad block map with some proprietary command.
@Wolf480pl @izaya Ah, in practice you can keep using SSDs drives normally for years without ever noticing a problem. In my personal experience, even the cheap Samsung EVO is way more reliable than 2.5" hard drives.
The desktop I'm typing on right now has an Intel SSD 320 from 2011 and an Intel SSD 520 from 2012 for root and home. These drives came from my old Thinkpads and were used every day heavily.