Files
2026-10-31 08:34:17 -06:00

33 lines
1.9 KiB
Markdown

---
title: "Bitwarden"
category: "Backup, files and security"
tagline: "An open-source password manager that syncs across your devices and doubles as your SSH agent."
source: "pacman"
package: "bitwarden"
command: "bitwarden-desktop"
replaces: ["1Password", "LastPass"]
website: "https://bitwarden.com/"
code: "https://github.com/bitwarden/clients"
links:
- name: "Bitwarden SSH agent"
url: "https://bitwarden.com/help/ssh-agent/"
---
## What it is
Bitwarden is a password manager. It keeps your passwords, passkeys, card details and secure notes in an encrypted vault that only your master password can open, and syncs it between the desktop app, your phone and browser extensions.
The desktop app can also store SSH keys and act as an SSH agent, so `ssh` and `git` ask Bitwarden for a key instead of reading one from `~/.ssh`.
## Why it's here
- **Open source and audited.** The clients and server code are public, and the encryption happens on your device.
- **Everywhere you are.** The same vault works on Linux, Windows, macOS, Android, iOS and in every major browser.
- **Somewhere safe for the important things.** Such as the backup passphrase `configure` shows you once.
## On CoreDesktop
CoreDesktop installs the Bitwarden desktop app from pacman. Open it from the app menu, or run `bitwarden-desktop`. Install and every `update` make sure your `~/.bashrc` has a line that points `SSH_AUTH_SOCK` at `~/.bitwarden-ssh-agent.sock` while Bitwarden is running its SSH agent, and leaves it on GNOME's agent otherwise. So once you turn on the SSH agent in Bitwarden's settings, terminals opened after Bitwarden starts use the keys in your vault; a terminal opened before then uses GNOME's agent, so open a new one.
When you set up [backups](/utilities/#configure), save the passphrase in Bitwarden. The [AI sandbox](/ai-sandbox/) keeps agents out of `~/.config/Bitwarden`. `update` keeps Bitwarden current with the rest of the Arch packages.