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 are viewing a single thread.
View all comments
2 points

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?

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.3K

    Monthly active users

  • 3.7K

    Posts

  • 81K

    Comments