this post was submitted on 18 Jun 2025
29 points (93.9% liked)

Selfhosted

46672 readers
865 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
29
Encrypting without full disk encryption question (piefed.ca)
submitted 14 hours ago* (last edited 14 hours ago) by teppa@piefed.ca to c/selfhosted@lemmy.world
20 comments fedilink hide all child comments
 

I use a headless server connected to nothing but an ethernet cable in my basement, and I'd prefer to allow the thing to boot by itself and start up without me needing to unlock the disk encryption every single time I do an update or power back on. Its a Dell 9500t NUC that I'm using it as a server and am wondering whether its possible to encrypt everything still.

I do generally use docker containers, so could I potentially encrypt just the containers themselves, assuming I'm worried about a smash and grab rather than someone keeping the machine powered up and reading my ram?

you are viewing a single comment's thread
view the rest of the comments
[–] theunknownmuncher@lemmy.world 27 points 14 hours ago (1 children)

If it can power up and decrypt the docker volumes on its own without prompting you for a password in your basement, it will also power up and decrypt the docker volumes on its own without prompting the robbers for a password in their basement

[–] morethanevil@lemmy.fedifriends.social 8 points 13 hours ago (1 children)

Exactly, I don't get why people want (full disk) encryption, but with automounted keyfiles after reboot 😂

[–] ryokimball@infosec.pub 6 points 13 hours ago (2 children)

First reason I think of to use fde all the time even if it's automatically unlocked, is it's simple to securely delete everything all at once. Just delete all the keys or overwrite that section of the desk.

[–] lorentz@feddit.it 2 points 7 hours ago

Second reason. It may run your vpn, with the server down you cannot connect to it and provide the decryption key unless you are connected to the same network.

There are some good answer around where the server can easily decrypt automatically as long as it is connected in your home but will likely fail at a thief's home. These are a much safer setup than keeping data unencrypted even if they are not bullet proof.

[–] catloaf@lemm.ee 0 points 13 hours ago (1 children)

Depends on how you want to define "securely". A sufficiently motivated attacker could attack the remaining encrypted data, either through brute force or exploiting a weakness in the algorithm.

[–] ftbd@feddit.org 4 points 10 hours ago

If you find an encrypted drive, it's extremely unlikely you can recover anything from it. If there is no LUKS header, it's pretty much impossible.