Arch Linux User Repository

There's a mismatch between the post install note in bitwarden.install and the bitwarden.sh custom launch script.

The note in bitwarden.install states:

post_install() {
  note "Custom flags should be put directly in: ~/.config/bitwarden.conf"
}

However, the bitwarden.sh custom launch script reads:

# Allow users to override command-line options
if [[ -f "$XDG_CONFIG_HOME/bitwarden-flags.conf" ]]; then
   BITWARDEN_USER_FLAGS="$(grep -v '^#' "$XDG_CONFIG_HOME/bitwarden-flags.conf")"
fi

I propose the note in bitwarden.install to be updated to reflect what the launch script actually does and to keep it in line with other packages that do something similar, e.g. visual-studio-code-bin, chromium, google-chrome, microsoft-edge-stable-bin etc.

@zeroz: That is neither an issue with this package nor any other. Please see Disable debug packages and LTO. Only use the debug flag manually when you actually need to debug something.

r2modman-bin-debug: /usr/lib/debug/.build-id/df/28017d426455b189e0f1bb054805f3fec8f3e7 exists in filesystem (owned by bitwarden-bin-debug) r2modman-bin-debug: /usr/lib/debug/.build-id/df/28017d426455b189e0f1bb054805f3fec8f3e7.debug exists in filesystem (owned by bitwarden-bin-debug)

The build id of this, conflicts with other debug packages, including r2modman and mullvad-vpn yay packages

+1 Had to install this because the official repo version has a bug preventing ssh agent from working. In case search engines crawl this, the issue manifests in rclone with this error:

CRITICAL: Failed to create file system for "remoteName:": couldn't connect to ssh-agent: Error connecting to SSH_AUTH_SOCK: dial unix /home/yourUsername/.bitwarden-ssh-agent.sock: connect: connection refused

See: https://github.com/bitwarden/clients/issues/14617

Yup, the real issue here is simply that the package in extra has been out of date for months now with nothing being done about it

There is a reason to use this over the package in [extra]: this one is actually up-to-date. There are currently features that are missing in the mainline package, such as the ability to configure the ssh agent authorization methods.

Generally, I would rather my password/secrets manager be kept up-to-date by the distro.

Is there as of now any reason to use this package over extra/bitwarden? Meaning has this package been obsoleted by extra/bitwarden?

Thanks for adding support to bitwarden.conf. But since this is an electron app, it should also read electron.conf. Do you want to also add this?