-
Notifications
You must be signed in to change notification settings - Fork 71
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
Forward ssh-agent socket into the sandbox #33
Comments
This could alleviate #23 as well: in my usage, I'm mostly using keys enrolled into the session-provided agent. |
I agree with @mzabaluev, that would great to be able to do so out of the box! |
This requires at least flatpak 0.10.3 (releases before then fail when they see unknown permissions). We only have flathub version stats from Flatpak 0.11.3 onwards, and that or newer is currently at 60% of usage. I'd love to see that get higher before we turn this on by default. (we believe the main 'offender' is CentOS/RHEL which are on 0.8.8 fwiw.) |
For an individual installation, the problem can be solved persistently with |
Should be fixed by 4d6ea9a |
To facilitate working with git over ssh, it would be nice if the sandbox had access to the ssh-agent socket from the user session. flatpak/flatpak#1438 says this is feasible with manual override options of
flatpak run
, but it would be great if the app had it out of the box.The text was updated successfully, but these errors were encountered: