bw_web_builds VS Bitwarden

I upgraded to this: https://github.com/dani-garcia/bw_web_builds/releases/tag/v2023.2.0

downloaded the latest web vault release from https://github.com/dani-garcia/bw_web_builds, extracting it to the web-vault subdir,

The repository you are looking for is this one bw_web_builds. It basically checks out this official bitwarden repository and applies the patches under the /patches folder. It also has instructions for how to create your own patches by modifying the original repo and running a git diff command.

Dependencies required: brew (https://brew.sh/) postgreSQL: brew install postgresql nodejs12: brew install node@12 node-sass: brew install node-sass rust dev version: brew install rustup-init nginx: brew install nginx vaultwarden for macOS with postgreSQL ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ git clone https://github.com/dani-garcia/vaultwarden ./vaultwarden cd vaultwarden git checkout "$(git tag --sort=v:refname | tail -n1)" cargo build --features postgresql --release Congratulation, you have built a macOS binary for vaultwarden For web-vault (if you need it) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ git clone https://github.com/bitwarden/web.git web-vault cd web-vault Open a web browser and go to https://github.com/dani-garcia/bw_web_builds to see latest available patch for vaultwarden git checkout v2.20.4 git submodule update --recursive --init export WEB_VERSION=v2.20.4 curl https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/${WEB_VERSION}.patch >${WEB_VERSION}.patch git apply ${WEB_VERSION}.patch -v npm config set python /usr/local/bin/python3 npm install npm run dist Congratulation, you have built the web vault Post compile instructions ~~~~~~~~~~~~~~~~~~~~~~~~~ Vaultwarden binary can be found in the vaultwarden/target/release directory web-vault pack can be found in the vaultwarden/web-vault/build directory now you can create a "ditribution directory" where you want, for example: /data/vaultwarden /data/vaultwarden/web-vault and copy the binary directory with: cp -R PATH/vaultwarden/target/release/ /data/vaultwarden cp -R PATH/vaultwarden/web-vault/build/ /data/vaultwarden/web-vault modify PATH/vaultwarden/.env.template with the path and settings you want cp PATH/vaultwarden/.env.template /data/vaultwarden/.env To automatically start vaultwarden at boot (after powerfailure) create a plist in /Library/LaunchDaemons named vaultwarden.plist with this content and CHANGE change_username AND change_groupname to the user/group you want vaultwarden to be run as Label vaultwarden RunAtLoad KeepAlive UserName change_username GroupName change_groupname EnvironmentVariables PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin SHELL /bin/bash ProgramArguments /data/vaultwarden/vaultwarden WorkingDirectory /data/vaultwarden nginx proxy: server { if ($host = sub.example.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 10.0.1.2:80; server_name sub.example.com; } server { listen 443 ssl http2; server_name sub.example.com; ssl_certificate /data/letsencrypt/live/sub.example.com/fullchain.pem; # managed by Certbot ssl_certificate_key /data/letsencrypt/live/sub.example.com/privkey.pem; # managed by Certbot ssl_dhparam /data/letsencrypt/dhparams.pem; ssl_session_cache shared:SSL:10m; ssl_session_timeout 5m; add_header Alternate-Protocol 443:npn-spdy/3; add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"; ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers 'TLS-CHACHA20-POLY1305-SHA256:TLS-AES-256-GCM-SHA384:TLS-AES-128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256'; ssl_early_data on; ssl_ecdh_curve secp384r1; server_tokens off; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; add_header Referrer-Policy no-referrer-when-downgrade; add_header X-Frame-Options "SAMEORIGIN" always; ssl_stapling on; ssl_stapling_verify on; error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/local/opt/nginx/html; } location /robots.txt { return 200 "User-agent: *\nDisallow: /"; } location / { root /data/vaultwarden/web-vault; proxy_pass http://10.0.1.2:9000; client_max_body_size 100M; # Limit Document size to 100MB proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub/negotiate { root /data/vaultwarden/web-vault; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http://10.0.1.2:9000; } location /notifications/hub { root /data/vaultwarden/web-vault; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://10.0.1.2:3012; } } brew services restart nginx sudo launchctl load /Library/LauchDaemons/vaultwarden.plist Vaultwarden should be up and running

You can take a look at the latest patch file to see the changes from the official Bitwarden web vault. The main difference is probably that it now says "© 2021, Bitwarden Inc. (Powered by Vaultwarden)" in the footer.

I was looking through the Bitwarden server repository (https://github.com/bitwarden/server ) and was surprised to see that no comments (xml or otherwise) were availible.

Is this normal in an entreprise setting? I thought it was standard to comment every public member (Visual Studio warnings).

For passwords and 2FA I use Bitwarden in combination with a self-hosted Vaultwarden service (for imcreased security and use of pro features for free).

First it's good to use a password manager, however it's not a good idea to use the one built into your browser. I would suggest switching to BitWarden or similar (not LastPass).

I just noticed today when relogging in on Bitwarden (I couldn't sync my vault) that it said "Logged in as [email] on __$2__" instead of "Logged in as [email] on bitwarden.com". I don't know why or how that happened, and I have no idea what it means. Did I screw up somehow? Just to be clear, I did login and just after I logged in my brain realized that it said "__$2__" instead of what it should say.

bitwarden:~$ sudo ./bitwarden.sh updateself _ _ _ _ | |__ (_) |___ ____ _ _ __ __| | ___ _ __ | '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ | |_) | | |_ \ V V / (_| | | | (_| | __/ | | | |_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_| Open source password management solutions Copyright 2015-2023, 8bit Solutions LLC https://bitwarden.com, https://github.com/bitwarden =================================================== bitwarden.sh version 2023.10.3 Docker version 24.0.7, build afdd53b Docker Compose version v2.21.0 Updated self. bitwarden:~$ sudo ./bitwarden.sh update _ _ _ _ | |__ (_) |___ ____ _ _ __ __| | ___ _ __ | '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ | |_) | | |_ \ V V / (_| | | | (_| | __/ | | | |_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_| Open source password management solutions Copyright 2015-2023, 8bit Solutions LLC https://bitwarden.com, https://github.com/bitwarden =================================================== bitwarden.sh version 2023.10.3 Docker version 24.0.7, build afdd53b Docker Compose version v2.21.0 Update not needed bitwarden:~$

Bitwarden (version 8588): A secure and free password manager for all of your devices.

I would also recommend the use of a password manager such as Proton Pass, BitWarden or 1Password if your looking for a more premium solution.