Package Details: bitwarden_rs 1.14.1-1

Git Clone URL: https://aur.archlinux.org/bitwarden_rs.git (read-only, click to copy)
Package Base: bitwarden_rs
Description: An unofficial lightweight implementation of the bitwarden-server using rust and sqlite. Does NOT include the web-interface.
Upstream URL: https://github.com/dani-garcia/bitwarden_rs
Keywords: bitwarden manager password passwordmanager rust selfhosted server
Licenses: GPL3
Conflicts: bitwarden_rs-git, bitwarden_rs-mysql, bitwarden_rs-postgresql
Submitter: mqs
Maintainer: mqs
Last Packager: mqs
Votes: 9
Popularity: 0.097301
First Submitted: 2018-07-13 15:29
Last Updated: 2020-03-21 21:25

Pinned Comments

grawlinson commented on 2020-02-18 05:34

If any users are running this in a container (LXC, et al), the systemd service will not start. The line LimitNPROC=64 in the service file prevents the service from starting, as the following error shows:

Feb 18 05:29:10 staging-bitwarden systemd[1]: Started Bitwarden Server (Rust Edition).
Feb 18 05:29:10 staging-bitwarden systemd[49506]: bitwarden_rs.service: Failed to execute command: Resource temporarily unavailable
Feb 18 05:29:10 staging-bitwarden systemd[49506]: bitwarden_rs.service: Failed at step EXEC spawning /usr/bin/bitwarden_rs: Resource temporarily unavailable
Feb 18 05:29:10 staging-bitwarden systemd[1]: bitwarden_rs.service: Main process exited, code=exited, status=203/EXEC
Feb 18 05:29:10 staging-bitwarden systemd[1]: bitwarden_rs.service: Failed with result 'exit-code'.

Commenting out that particular line results in the service starting correctly.

oguresic commented on 2020-01-07 08:14

For aarch64 architecture I got the following compiling error in cargo:

linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64

It is due to binutils update from 2.32 to 2.33 and I assume the -fix-cortex-a53-835769 --fix-cortex-a53-843419 flags lead to an invalid operation.

To fix this downgrade to binutils 2.32 Version.

I had it in my /var/cache/pacman/pkg/binutils-2.32-1-aarch64.pkg.tar.xz and was able to rollback it by using pacman -U binutils-2.32-1-aarch64.pkg.tar.xz.

Latest Comments

1 2 3 Next › Last »

Inxsible commented on 2020-03-10 14:43

Thank you again @grawlinson & @mqs.

If the chrome/firefox extension would work without issues, then I will try to only install the bitwarden_rs server. If in the future I feel the need to access it via a browser, then I can replace it with the vault version.

Thanks for helping me understand.

mqs commented on 2020-03-10 06:38

@Inxsible You only need the web vault if you want to access it as a web page, e.g. from devices other than your own or devices where you can't even install browser plugins or apps. If you are using a Chromebook, you can probably use the official Bitwarden browser plugin and won't need the web-vault.

If you do want to install bitwarden_rs-vault, you probably won't have to reconfigure bitwarden_rs.env because the vault package will try to configure it automatically. Just follow the instructions shown when you install the package. If you want to use it in chrome then I recommend bitwarden_rs-vault-bin because it already was patched to mitigate a chrome bug.

grawlinson commented on 2020-03-10 05:54

Yes, the documentation is a bit sparse.

For your use-case, you'll want to install bitwarden_rs and bitwarden_rs-vault, you'll also want to setup a reverse proxy with HTTPS as well as modify /etc/bitwarden_rs.env as below:

## Web vault settings
WEB_VAULT_FOLDER=/usr/share/bitwarden_rs/vault
WEB_VAULT_ENABLED=true

There are other variables that need adjusting, the wiki has examples in the 'Configuration' section.

If you need additional help, my contact details can be found in my profile.

Inxsible commented on 2020-03-10 05:09

@grawlinson, thank you. so the web-vault is used only if you want to use the passwords via a browser?

I intend to use it on a chromebook as well -- so if the answer to the above question is yes, then I assume I would need to install the web-vault, correct?

Sorry, I just didn't find clear information related to why web-vault is needed on the bitwarden_rs github page. Once I self host on my server, I intend to use the password manager across all my devices - Android phones and tablets, Archlinux desktop and other containers on my server & Chromebook.

grawlinson commented on 2020-03-10 04:54

@Inxsible - Some people don't want the web vault, and would prefer only to use the server backend with dedicated clients; iOS, Android, Desktop, et al.

bitwarden_rs is a complete reimplementation of the bitwarden backend, and bitwarden_rs-vault is upstream's vault patched to make it work with bitwarden_rs.

EDIT: If you want to utilise the web vault, then you do need to install that second package.

Inxsible commented on 2020-03-10 04:31

The one thing that is not quite clear to me is: Do I need the web-vault if I am self hosting? If yes, then why do you have 2 separate packages -- one with and one without the web-vault?

Thanks.

grawlinson commented on 2020-02-18 05:34

If any users are running this in a container (LXC, et al), the systemd service will not start. The line LimitNPROC=64 in the service file prevents the service from starting, as the following error shows:

Feb 18 05:29:10 staging-bitwarden systemd[1]: Started Bitwarden Server (Rust Edition).
Feb 18 05:29:10 staging-bitwarden systemd[49506]: bitwarden_rs.service: Failed to execute command: Resource temporarily unavailable
Feb 18 05:29:10 staging-bitwarden systemd[49506]: bitwarden_rs.service: Failed at step EXEC spawning /usr/bin/bitwarden_rs: Resource temporarily unavailable
Feb 18 05:29:10 staging-bitwarden systemd[1]: bitwarden_rs.service: Main process exited, code=exited, status=203/EXEC
Feb 18 05:29:10 staging-bitwarden systemd[1]: bitwarden_rs.service: Failed with result 'exit-code'.

Commenting out that particular line results in the service starting correctly.

oguresic commented on 2020-01-07 08:14

For aarch64 architecture I got the following compiling error in cargo:

linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64

It is due to binutils update from 2.32 to 2.33 and I assume the -fix-cortex-a53-835769 --fix-cortex-a53-843419 flags lead to an invalid operation.

To fix this downgrade to binutils 2.32 Version.

I had it in my /var/cache/pacman/pkg/binutils-2.32-1-aarch64.pkg.tar.xz and was able to rollback it by using pacman -U binutils-2.32-1-aarch64.pkg.tar.xz.

mqs commented on 2020-01-05 21:42

Thanks! I'll push an update soon.

Siosm commented on 2020-01-05 19:40

  • Is this safe to migrate to without any changes?

Yes, I think it is. Both tmpfiles & sysuser configuration will be a NOP if user & folder already exists.

  • I assume that /var/lib/bitwarden_rs isn't changed/removed in any way between service stop and the next (re-)start?
  • What happens to the /var/lib/bitwarden_rs directory after the package (and the corresponding tmpfiles file) is removed?

The 'd' specifier in the tmpfiles configuration will only create the directory or update the Mode/Owner. The content is unchanged and not subject to regular cleanup (see https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html#d). The 'check' is done when systemd-tmpfiles is called, which is usually at bootup.

Nothing happens if the package is removed: the directory & the user are not removed. Both tmpfiles & users config are additive by default (idempotent to be precise). There is no "state" which would trigger a removal.

The name is indeed confusing at first. I have not yet fully check that my changes work but I will soon and post an update.