The ssh-keys interface doesn't expose access to host ssh-agent

Bug #1826747 reported by 林博仁(Buo-ren, Lin)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Wishlist
Unassigned

Bug Description

As title, AFAICT the `host's SSH_AUTH_SOCK` records the socket to communicate with the ssh-agent process, however, its value(`/tmp/ssh-XXXXXXXXXXXX/agent.XXXXX` in Ubuntu) isn't available in the snap runtime environment, essentially blocking communication to the ssh-agent process running on the host.

summary: - ssh-keys interface doesn't exposed access to ssh-agent
+ The ssh-keys interface doesn't exposed access to ssh-agent
summary: - The ssh-keys interface doesn't exposed access to ssh-agent
+ The ssh-keys interface doesn't expose access to host ssh-agent
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

At least on Ubuntu 19.04 the socket is now placed in /run, making it accessible:

zyga@fyke:~$ echo $SSH_AUTH_SOCK
/run/user/1000/keyring/ssh

Having said that, there is no interface exposing access to the agent. I'm marking this as confirmed / whishlist, as this is a new feature. Please escalate to have it investigated faster.

Changed in snapd:
status: New → Confirmed
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers