S
@x_cli To give you more context, here are some screenshots of how KeePassXC implements things.
I use KeePassXC inside an off-the-grid VM on @QubesOS. It's a great way the keep all my secrets and the ones of my clients at @SkypLabs safe.
The communication with the SSH agent that actually handles the connection is made via qrexec, in internal Qubes OS RPC mechanism (see https://forum.qubes-os.org/t/split-ssh/19060).
@x_cli From what I understood, the issue is that the built-in Bitwarden SSH agent loads all the available keys at once, potentially triggering the server-side max limit.
The approach I was considering is to add the possibility to load only specific keys into the Bitwarden built-in agent. It's exactly what I do with KeePassXC and its SSH agent.
@x_cli Have you considered reporting the issue to Bitwarden (even though I suppose it's already known), and why not contributing to it to fix it?
@thelocalstack Not yet, but I will!
