Loadscreen210

• Bitwarden Exploit
• Bitwarden Explorer
• Bitwarden Extension Edge
• Bitwarden Linux

1. Bitwarden has password managers for Windows, Mac, iOS, and Android and browser extensions for Chrome, Firefox, Safari, Edge, and Tor. You can also manage log-in info through the cloud and create.
2. We are 3 people, including myself, and we support all our customers together. If we all need to have access to all our customer's credentials in Bitwarden, we'd have to create 100 organizations with 3 users each. That's $900 per month before even a single customer actually received access to their credentials.
3. Use it for a personal, team, or an entire organization. Bitwarden uses multi-security algorithms and available as self-hosted or SaaS. If you choose to self-host, you can do it on Windows, Linux, macOS, and Docker. Let’s check out some of their features. Audit trail of user’s action.

Bitwarden Extension results in significant lag OS X Chrome Browser Like many of you I switched to Bitwarden after Last Pass started charging for 1 device. After I installed the Chrome extension I noticed that typing in gmail would be lagged.

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

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

Bitwarden Exploit

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.

Bitwarden Explorer

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

Bitwarden Extension Edge

Read this article.

Debugging/FAQ

Bitwarden Linux

Show running docker containers

Logs and events

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.