I’m planning to set up LUKS on an SSD. Many guides are suggesting using a simple key to set things up and then revoke it when everything is in place.
Given the wear leveling behavior on SSDs I am assuming a simple key might be able to unlock even beyond the revocation if a determined attacker has the disk. I don’t want someone to be able to put the disk in factory access mode and be able to brute force attempt their way to browser cookies and email accounts.
I’m going to ignore the suggestion about using a weak key to set up, but am I being overly paranoid? Am I being not paranoid enough and I should also not rely on revocation for a spinning rust disk?
You must log in or # to comment.
Use cryptsetup and it should handle key creation for you. I’ve never heard this but about key revision. How are you supposed to use the disk if the key is revoked?
Hdd’s have bad block remapping sort of like ssd’s, so the same issues apply to both types of media.
Ive always used cryptsetup and never seen any intructions like how you are describing. I wonder if you have a different use case than I do? It seems like adding more complexity to start with one decryption method only to change it soon. Why?
