-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Feature/export ssh auth sock #1307
Conversation
Woohoo, this looks really good. One question: What happens if SSH_AUTH_SOCK is not set on the user's machine? Should we just ignore probably? or warn? |
I added a warning message so the user is warned. This would happen when no agent forwarding was allowed in ssh conf, for example. Feel free to change it according wuth you style gudielines. Thanks for vagrant by the way!! |
👍 |
Is this going to be merged in soon? Would be great to have this fixed :-) |
👍 This is a great fix to the agent forwarding problem because it doesn't require a change to the |
This has finally been merged! :) I made some modifications to how 1071a09f61f81c7983f06788355814fc57994bc4 |
this is broken. in my setup printf is called with no arguments, and resulting an printf error. if printf is used at least format
|
the actual problem why forwarding did not work, was that
|
When using puppet/chef providers a sudo is issued from inside the vm. The thing is that if SSH_AUTH_SOCK is not set once in sudo, ssh-agent-forwarding will not work. This is due to the fact that sudo erases the environment unless set otherwise in sudoers file.
Given that there is a configuration variable to set agent forwarding, and that we can not make any asumptions of how /etc/sudoers is configured, it makes sense to correctly export that variable when we are using sudo and agent forwarding is set in the Vagrant file.