Selfhosted

40211 readers

1420 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

How safe is revoking a LUKS key on flash media? (lemmy.ml)

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

7 comments fedilink hide all child comments

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

[–] jkrtn@lemmy.ml 1 points 9 months ago (1 children)

I think yeah, I will not be following that advice for sure. Just wondering at this point if someone should take extra precautions around SSD encryption. Like should one overwrite the whole drive if a key is leaked so that the odds of recovering any info from the chips is lessened? Or is revoking the leaked key sufficient?

[–] avidamoeba@lemmy.ca 1 points 9 months ago

It all depends on the threat model. If I were protecting against accidental data disclosure after decommissioning an SSD, then revoking would suffice. However if I were a journalist gathering data on some unsavory state subjects, I'd probably only ever use high-entropy keys.