I’ve recently updated Bitwarden and it has started to hijack the Windows pipe for the open-ssh-agent.
I use 1Password for my SSH keys and do not want Bitwarden to handle them or have the agent running, however despite never checking the box and trying to check then uncheck, restart etc; The pipe open every time.
It seems like this may be bug.
Thanks for sharing, we’re looking into this one!
On Linux (Arch Linux) it’s also behaving strangely. Not hijacking the normal one, but it does start its own SSH agent and creates the socket file for it even though the SSH agent option is disabled in the settings:
[SSH Agent Native Module] BITWARDEN_SSH_AUTH_SOCK not set, using default path
[SSH Agent Native Module] Starting SSH Agent server on "/home/sharparam/.bitwarden-ssh-agent.sock"
[SSH Agent Native Module] Could not remove existing socket file: No such file or directory (os error 2)
23:52:19.389 › SSH agent started
Not sure how long this has been a thing because I haven’t noticed it until looking at the logs trying to troubleshoot a different problem.
Bump. This is also a problem with KeePass and KeeAgent. Silly me for believing that when an option is unchecked that it is indeed off. Bitwarden should not co-opt the named pipe if the feature is turned off. Spent an afternoon tracking this one down. The bill is in the mail.
I’ve opened this GitHub issue: [Windows] Disabling ssh-agent still claims the socket · Issue #13150 · bitwarden/clients · GitHub