-
Notifications
You must be signed in to change notification settings - Fork 103
SSH-agent protocol #197
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
Comments
this would probably be possible, but i don't know that it is entirely necessary? i solve this issue by using a wrapper script for |
Even if I developped https://framagit.org/Glandos/bw-ssh/ it seems that SSH keys are becoming a reality, at least in Vaultwarden: dani-garcia/vaultwarden#5187 |
any update , because the app seems to work well with the integration |
The first step would be to implement the new SSH Key items added to the vault. With this, one could easily make a ssh agent using rbw if @doy decides that adding an ssh agent is out of scope for this project. @doy are you planning to implement the new SSH Key items, or would you accept a patch for this? |
Just an idea:
Do you think the current
rbw
agent can be extended to perform SSH agent protocol by directly retrieving ssh keys from entries withinrbw
(e.g. supplying ssh-keys with bitwarden items that begins with name prefix likeSSH_KEY_xxxx
)This crate seems relevant to this idea:
https://docs.rs/ssh-agent-lib/latest/ssh_agent_lib/
The goal would be removing the needs to store secret key directly on machines
The text was updated successfully, but these errors were encountered: