On linux with bitwarden flatpak: no `.bitwarden-ssh-agent.sock`

Fred_Eisele · March 26, 2025, 7:19pm

I installed the Bitwarden flatpak and enabled the ssh agent.

However, I do not see the socket when I look for it.

# Flatpak
export SSH_AUTH_SOCK=/home/<user>/.var/app/com.bitwarden.desktop/data/.bitwarden-ssh-agent.sock

Fred_Eisele · March 26, 2025, 7:42pm

I think this is a know bug.

github.com/bitwarden/clients

SSH Agent doesn't work with Flatpak version

opened 07:51PM - 30 Jan 25 UTC

closed 01:47PM - 25 Feb 25 UTC

WindFreaker

bug desktop

### Steps To Reproduce 1. Follow the [Bitwarden SSH Agent](https://bitwarden.co…m/help/ssh-agent/#tab-snap-6VN1DmoAVFvm7ZWD95curS) guide. ### Expected Result The SSH Agent works. ### Actual Result The SSH Agent doesn't work. ### Screenshots or Videos _No response_ ### Additional Context With the latest release 2025.1.3 the SSH Agent functionality doesn't work with flatpak version of Bitwarden. In my testing I have run into two issues: 1. The client fails to create the `.bitwarden-ssh-agent.sock` file. - The client attempts to create the file at the default directory `/home/<user>/.bitwarden-ssh-agent.sock` but fails due to lacking filesystem access. - This can be worked around by either granting the app access to the user's home directory or by settings the `BITWARDEN_SSH_AUTH_SOCK` environment variable to something the client can access, such as `/home/<user>/.var/app/com.bitwarden.desktop/.bitwarden-ssh-agent.sock` 2. Usage of SSH hangs after setting the `SSH_AUTH_SOCK` environment variable. - This result can be observed running `ssh-add -L` after setting the `SSH_AUTH_SOCK` environment variable. - The first time running the command will fail with the error `communication with agent failed` but subsequent attempts hang. - I have not discovered a fix for this block yet. ### Operating System Linux ### Operating System Version Fedora 41 ### Installation method Other ### Build Version 2025.1.3 ### Issue Tracking Info - [x] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.