7
submitted 9 months ago by jkrtn@lemmy.ml to c/selfhosted@lemmy.world

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 comment's thread
view the rest of the comments
[-] solrize@lemmy.world 3 points 9 months ago

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.

[-] Gooey0210@sh.itjust.works 2 points 9 months ago

The op probably meant removing one key and adding another

[-] jkrtn@lemmy.ml 2 points 9 months ago

Yes. Some guides suggest, say, "just use 'key' for now, we'll replace it later." I didn't mention their step adding a stronger key, I guess I didn't see that as an important part of the question.

[-] solrize@lemmy.world 1 points 9 months ago

I've never done it that way and don't see the benefit. Am I missing something? Of course for a testing setup just do something easy. But don't store any sensitive data under a weak key, ever.

this post was submitted on 31 Jan 2024
7 points (76.9% liked)

Selfhosted

40133 readers
545 users here now

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!

founded 1 year ago
MODERATORS