Selfhosted
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!
view the rest of the comments
I'd be very suspicious at what else this guide has for you if it advises to use "key" passphrase for a LUKS key.
With that said, most SSDs do encrypt data before it reaches the NAND. I don't know what "factory access mode" is and whether that can get around it.
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?
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.