min

joined 1 year ago
[–] [email protected] 1 points 6 days ago

Do note, because it's using email, the recipient and sender are not private, along with the time, and probably the relative size of the messages.

The specific content of each message should be private as long as the encryption is done well. I haven't looked at it so I don't know if it implemnts safeguards to verify who you're messaging with (besides using the email address) and I don't know if it uses PFS (Perfect Forward Secrecy) to protect against a key getting compromised.

[–] [email protected] 3 points 1 week ago (2 children)

https://github.com/rsmsctr/vaultwardenGuide

It doesn't cover backups though. It uses Caddy instead of NGINX, and it uses DuckDNS to point a subdomain to your private IP address of your Vaultwarden server, so it will only be accessible in your LAN.

[–] [email protected] 8 points 2 weeks ago (1 children)

I've been researching zero-trust for my homelab recently and I'm considering OpenZiti instead of Cloudflare since I think it can all be self-hosted. The BrowZer from OpenZiti is especially interesting to me. The fact that I'm behind CGNAT is a hurdle though.

[–] [email protected] 4 points 3 weeks ago

It ends up being a lot like FIDO or Passkeys but without having to store a separate key for each site. Each key is derived from your master key and the domain so they are all unique, to prevent tracking, but you still don't have to save a separate private key blob for each site. There is also a recovery key built into the spec so that if your master key somehow gets out, you can use your recovery key to prove you're the real person and regain your account to change the signin public key.

[–] [email protected] 6 points 3 weeks ago (2 children)
[–] [email protected] 7 points 5 months ago

Something that always bothered me about that episode.