What are the best practices for using Bitwarden with IP protection proxies? For example, the Firefox web browser now has an integrated “VPN”, which is really a proxy. Some other web browsers include similar functionality, and external 3rd-parties also provide such proxy services.
Trust of the company providing the service may be important. But unless you personally know and trust everyone working at the provider, you will never know everything that is really going on (which is why self-hosting is often a good idea, but that is much less feasible in this context).
How important is trust of the proxy service, actually? If Bitwarden is properly designed and coded, even MITM attacks should be mitigated. Of course, proper design and code are rarities, as a concerning recent report about password managers reflects.
Are there any best practices, tips, or concerns regarding the intersection of Bitwarden and proxies?
I don’t know what the best practices are, but right now I agree that given the massive surveillance governments and private companies have on individuals, and given governments may change their minds at any moment about what’s no good, doing anything easy can push a person ahead of the curve in terms of exposing their real identity and affiliations.
Bitwarden used to block IP addresses, but I think that practice has stopped and nobody’s been complaining recently. Bitwarden seems fine with VPNs now, though I’m not sure if that’s true for all VPN services and proxies.
I personally wouldn’t choose to use any questionable VPNs or proxies. As far as I know, MITM isn’t possible at the protocol level (TLS/HTTPS). If you only use unphishable authenticators (and don’t enable “remember” options for unphisable 2FA), being careful/certain about your software usage, scams, and phishing, MITM seems like a manageable risk.
Hi @bit! Generally speaking, Bitwarden is compatible with a wide variety of IP protection proxies and VPNs - it’s really up to you and your security posture.
