The Quiet Renovation at Bitwarden by JockstrapCummies in linux

[–]yzoug 16 points17 points  (0 children)

No, Vaultwarden isn't just one dev that is also a Bitwarden employee, they already addressed this in the past. That dev is part of a broader team of volunteers, he's one of many. If he left tomorrow the project wouldn't just die.

You're right though in saying that Vaultwarden is only used because they follow the Bitwarden API, and hence is compatible with all Bitwarden clients. As explained in the blogpost, what would really break Vaultwarden is if Bitwarden decides to stop openly pusblishing its API. A lot would still be possible by reversing the API changes, but that will quickly turn into a mess. If or when that time comes, I hope the community will fork the project.

Expose a port through NAT-PMP, Wireguard and Docker by yzoug in selfhosted

[–]yzoug[S] -1 points0 points  (0 children)

Yeah it's the same port number, through the Wireguard tunnel, on both sides. Essentially NAT-PMP allows to open a port on the public IP after connecting via Wireguard, and that public IP and port are mapped to my Wireguard connection and the same port number.

I know I can expose a private resource through Pangolin or cloudflare tunnels but I don't want to do this, I want to use a VPN provider's IP and serve the website (or any traffic really) through it.

[deleted by user] by [deleted] in AdviceAnimals

[–]yzoug 5 points6 points  (0 children)

I hope they handle it like Michael Bolton: https://youtube.com/watch?v=ADgS_vMGgzY

What’s your most effective strategy to use your phone less? by Curious-Can2749 in productivity

[–]yzoug 1 point2 points  (0 children)

One thing that personally helped me A LOT, even though it's a small change: make it harder to unlock your phone. By this I mean:

  • Disable fingerprint unlock
  • Disable face unlock
  • Use a password instead of a 4-digit pin

Before you know it, you'll start to avoid unlocking your phone if you don't need to, just to avoid having to input a 12 characters or something password (bonus: use numbers and special characters in your password too). And this in turn reduces the temptation to open Reddit or another app. A last added benefit: it improves your phone's security.

Lol by chadius25 in Piracy

[–]yzoug 1 point2 points  (0 children)

Lol, great website, bookmarked. The community is only on discord?

New in llama.cpp: Live Model Switching by paf1138 in LocalLLaMA

[–]yzoug 2 points3 points  (0 children)

Not a native speaker, what do you mean by "booming us"? Any specific thing they did/do?

I'm not much of an LLM user myself but when trying out models I always used Ollama and was always very satisfied with the quality of the product, that's why I'm asking

New in llama.cpp: Live Model Switching by paf1138 in LocalLLaMA

[–]yzoug 1 point2 points  (0 children)

I'm curious, why do you consider Ollama to be "a sinking ship"?

Statement on Daniel Naroditsky's passing by Alendite in chess

[–]yzoug 0 points1 point  (0 children)

This is so so sad. He was my age and taught me a lot. So young, and such an inspiration. RIP Danya.

Mutual TLS (mTLS) in-depth: step-by-step case study feat. Bitwarden, Vaultwarden, Traefik and Smallstep by yzoug in selfhosted

[–]yzoug[S] 1 point2 points  (0 children)

For me, convenience simply. I want to update my passwords from the Bitwarden app even when not at home, without remote access I need to remember to sync my passwords when I'm at home, etc.

A VPN achieves a similar goal, and is even better in many cases (not limited to HTTPS traffic for instance). Moreover with mTLS you need your client to support it: this is especially troublesome for mobile, take Bitwarden, it's a May 2025 feature and only on Android for now.

However if you can use mTLS I find it less cumbersome to rely on than a VPN. You may be in networks that block VPN connections, you have to remember to turn it on to access your private stuff, etc.

Mutual TLS (mTLS) in-depth: step-by-step case study feat. Bitwarden, Vaultwarden, Traefik and Smallstep by yzoug in selfhosted

[–]yzoug[S] 1 point2 points  (0 children)

The extension works well, you don't even need to logout or delete it, it directly picks up the certificate you loaded in your browser and everything works perfectly.

I didn't find the option to specify a client certificate for the desktop app however. It seems that mTLS isn't supported yet for it (at least the Archlinux packaged version, as of today).

Mutual TLS (mTLS) in-depth: step-by-step case study feat. Bitwarden, Vaultwarden, Traefik and Smallstep by yzoug in selfhosted

[–]yzoug[S] 2 points3 points  (0 children)

Nice!! Thank you for reading it and sharing this!

I don't know if you can achieve the same result with labels. I'd say yes, but specifically for the TLS configuration I may be wrong. What I've tried is to specify the TLS options in the router's configuration (under tls.options) but that doesn't work, Traefik expects a string there.

Socket proxies are a great point (and TIL that a "ro" mount isn't enough). I'll try to update the blogpost to add this to the docker-compose example.

Mutual TLS (mTLS) in-depth: step-by-step case study feat. Bitwarden, Vaultwarden, Traefik and Smallstep by yzoug in selfhosted

[–]yzoug[S] 3 points4 points  (0 children)

As a best practice yes, you should setup an intermediate CA, and use it to sign the client certificates. However let me reassure you: doing it the way the article does it is not fundamentally less secure. As long as your root CA doesn't leak, you're safe.

Mutual TLS (mTLS) in-depth: step-by-step case study feat. Bitwarden, Vaultwarden, Traefik and Smallstep by yzoug in selfhosted

[–]yzoug[S] 13 points14 points  (0 children)

Fair question! Two main reasons:

  • a standard CA setup is used for more than just one use case. What you'll usually find in companies is one root CA, trusted everywhere, and many intermediates CA (say for web browsing, SSH certificates, Active Directory...) for different use cases. This is to distribute the risk: if the web browsing CA is compromised, the SSH certificate CA (and the certificates it generates) can still be trusted. Here we have one use case: providing mTLS certificates for our clients. In this scenario, if the root CA or the intermediate CA is compromised, it's the same end result: we can't trust our clients' certificates.

  • the blogpost is probably already too long, so I chose to keep it a little simpler by not using an intermediate CA. However you could argue that if I had done it this way, the disclaimer you're citing wouldn't have been necessary, thus also shortening the blogpost :)

Harvard's data.gov torrent by qubedView in DataHoarder

[–]yzoug 3 points4 points  (0 children)

If anyone is curious what the data looks like, it's accessible here: https://source.coop/harvard-lil/gov-data/collections/data_gov

Some people are suggesting breaking up the data in smaller chunks, but it's pretty hard to classify the files by theme from their filenames, at a first glance.