Illiterate Domine

There are many ways to setups full disk encryption on Linux, but the most common all involve LUKS. Providing a password at mount (during boot, for a root partition or perhaps later for a “data” volume) is a but more secure and more frequently done, but you can also use things like smart cards (like a Yubikey) or a keyfile (basically a file as the password rather than typed in) to decrypt.

So, to actually answer your question, if you dont want to type passwords and are okay with the security implementations of storing the key with/near the system, putting a keyfile on removable storage that normally stays plugged in but can be removed to secure your disks is a common compromise. Here’s an approachable article about it.

Search terms: “luks”, " keyfile", “evil maid”

The difference, as I understand it, is Beeper hasn’t claimed to not be doing that. Sunbird/Nothing touted E2EE and that was a lie.

Most self-hosters are probably using dns services through their registrar, but you don’t have to. A registrar with poor api support might still be a good choice, if that was the only negative.

Well, I’m back and can confirm the sneaky DNS resolver. I have two roku devices and they both were making requests to 8.8.8.8.

Thanks for this post! TIL.

Interesting. I set an adblocking dns via DHCP and, as far as I know, the Roku respects it. Ads are blocked and I can see it failing to delivery telemetry in my dns logs (most persistent thing on the network).

I set a rule to catch outside dns to see if anything, the roku included, has been misbehaving.

If you have a phone number on the account, you can do an SMS reset. If not, I guess it’s “open a ticket with a throwaway” time.

There’s an optional subscription that includes all the DLC and makes crafting materials not consume inventory space. Crafting is really difficult without the sub, but the rest of the game is approachable without it.

Little clusters of nucs has become a really common way to run small Kubernetes clusters at home. I recently rebuilt mine (still using a bulky, power hungry box like you’re tossing) and have been very happy with it. Everything is really stable, containers that misbehave are automatically destroyed and replaced, and updates are breeze because everything lives in code/git.

Yeah, if that rolls out to more account types, you would no longer need the bridge for sending.

There’s a proton bridge docker container out there that I’m planning to standup this weekend for SMTP use inside my home lab.