Skip to content

SSH Agent Key usage confirmation often rejected accidentially #14261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
schuettecarsten opened this issue Apr 13, 2025 · 1 comment · May be fixed by #13995
Open
1 task done

SSH Agent Key usage confirmation often rejected accidentially #14261

schuettecarsten opened this issue Apr 13, 2025 · 1 comment · May be fixed by #13995
Labels
bug desktop Desktop Application

Comments

@schuettecarsten
Copy link

Steps To Reproduce

I use Bitwarden Desktop client on Windows 11 and integrated SSH Agent. If I try to login to an ssh server, I need to confirm key usage in Bitwarden's client window. That makes it neccessary to click into the window. If the confirmation dialog is shown and you click somewhere in the client are to bring the window to the front, this will reject the SSH request.

I also miss an option to auto-accept SSH key usage for specific keys. If you use rich GUI Git clients, you often get tons of confirmations when the Git clients try to fetch in background.

Expected Result

Notification to confirm key usage should be shown as real modal dialog or request should not be rejected when trying to bring the Bitwarden window to the front.

Actual Result

SSH requests are accidentially rejected when clicking in the client area.

Screenshots or Videos

Bitwarden Client in background, the confirmation dialog is shown somewhere in the client area, hard to find:
Image

Accidentially refused when clicking in the client area:
Image

Additional Context

No response

Operating System

Windows

Operating System Version

11

Installation method

Microsoft Store

Build Version

2025.3.0

Issue Tracking Info

  • 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.
@schuettecarsten schuettecarsten added bug desktop Desktop Application labels Apr 13, 2025
@S-Kakar
Copy link

S-Kakar commented Apr 13, 2025

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-20219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug desktop Desktop Application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants