Forward ssh keys to the remote VM. It would be \o/ Thanks to SSH_AUTH_SOCK, it is possible to forward your credentials. The protocol is described in http://api.libssh.org/rfc/PROTOCOL.agent, so a new channel may just forward all this to the client, which may in turn implement an agent or forward it to an existing agent?
(In reply to Marc-Andre Lureau from comment #0) > Forward ssh keys to the remote VM. It would be \o/ > > Thanks to SSH_AUTH_SOCK, it is possible to forward your credentials. The > protocol is described in http://api.libssh.org/rfc/PROTOCOL.agent, so a new > channel may just forward all this to the client, which may in turn implement > an agent or forward it to an existing agent? A prototype has been done, but the integration with the DE is still far away to be ready. Further discussions about the DE integration can be followed here: https://mail.gnome.org/archives/gnome-keyring-list/2015-September/msg00000.html Also, this is one suggestion to solve this problem: 13:21 < fidencio> elmarco: one option would be to have something like ssh-add --pipe /path/to/another_agent 13:22 < fidencio> so, it would be expanding the ssh-agent protocol and having a DE agnostic solution 13:22 < fidencio> it could be implemented in the gnome-keyring and in the openssh ... 13:22 < fidencio> elmarco: does it still sound bad to you? Links for further discussions and patches for libssh will be added here later.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice/issues/20.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.