Update (or install) the latest Bitwarden. GitHub Gist: instantly share code, notes, and snippets. Bitwarden is the easiest and safest way to store all of your logins and passwords while conveniently keeping them synced between all of your devices. Password theft is a serious problem. The websites and apps that you use are under attack every day. Security breaches occur and your passwords are stolen. Bitwarden offers a variety of different installation options for the desktop application. You can find them all listed below. Some options are not capable of automatic updates and are labeled as such. You should always keep Bitwarden applications up to date. 24.6k members in the Bitwarden community. Bitwarden is an open source password management platform for individuals, teams, and business organizations.

No, you don't synchronize a folder of Firefox, or any other browser. The Bitwarden server holds its own file containing the login/password data, and the information is sync'd across all your devices that are using Bitwarden. You don't download anything from any website.

Install Docker

Add user(s) to the docker group. The default user would be pi. However, I highly recommend deactivating the default user.

Reboot and then test docker

Install more dependencies

Bitwarden Files

Fight With SSL

This is the most annoying part of the story. You can either choose to use letsencrypt or a self-signed openssl-cert. Letsencrypt will only work, if your service will be exposed publicly. Also, letsencrypt is fairly easy to setup, so I will focus on a self-signed openssl-solution.

First, we’ll need a “virtual” certificate authority (CA) that will actually sign our certificate later. If you already have a CA, you can skip this. The first command creates a private key, the second command creates the root certificate of our CA.

Now, we’ll need to create a “client” key and a certificate signing request, which will then be “sent” to our CA.

For the actual signing, we’ll also need an extension file. I ran into problems with OSX and iOS without adding the used extensions during signing. Neither OSX, iOS nor Google Chrome accepted the certificate without those extensions. Create a file openssl.cnf

Replace <hostname> and <ip> with your actual values.

Finally, the actual signing:

The certificate you’ll need to deploy on your devices is the root certificate. Yes, this will also work on iOS.

Install/Configure Bitwarden

We’ll use the bitwarden_rs docker container. It uses sqlite instead of MSSQL, which is not available for ARM.

If docker successfully downloaded the image, you can run it as follows. I simply created a small bash script.

The ROCKET_TLS argument tells bitwarden, where it can find its key and certificate. The values describe paths within the docker container. For these paths to work, we’ll need to supply a volume mapping (-v). The additional volume mapping bw-data is a volume for bitwarden to store its actual sqlite “database” in. Internally, bitwarden will bind to port 80. Since we know/hope it’ll run SSL, we can map internal port 80 to 443.

If everything works, you can reach your bitwarden vaults on https://<hostname>

You’ll most likely run into SSL problems. Good luck.

Backup

Read this article.

Debugging/FAQ

Show running docker containers

Logs and events

Bitwarden Flaw

Run command within a docker container

Netstat (works w/o actual netstat binary in container. Cool, eh!?)

A word on IPv6. Initially, when bitwarden didn’t work during my first attempts, I was confused by the output of netstat. It showed, that the destination socket for https was only bound to tcp6. This shouldn’t be a problem, though, because bitwarden also sets up a couple of iptables rules (# iptables -L). However, if you think it might be a problem on your machine, try the following things in your /etc/sysctl.conf

At one point, I even completely disabled IPv6 via the kernel command line. However, that introduced even more problems.

Bitwarden Forum