blocks|key|499178|text|将其添加到Vagrantfile中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|499179|Vagrant::Config.run+do+%7Cconfig%7C
+++#+stuff
+++config.ssh.forward_agent+=+true
end|code-block|syntax|javascript|499180|See+the+docs|offset|length|499181|entityMap|0|LINK|mutability|MUTABLE|url|https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html#config-ssh-forward_agent^0|0|0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Add it to the Vagrantfile

<pre><code>Vagrant::Config.run do |config|
 # stuff
 config.ssh.forward_agent = true
end
</code></pre>

<a href="https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html#config-ssh-forward_agent" rel="nofollow noreferrer">See the docs</a>

blocks|key|499258|text|当我们最近在Vagrant+1.1.5中试用vagrant-aws插件时，我们遇到了一个关于SSH代理转发的问题。事实证明，Vagrant是在没有选择将其更改为no的情况下强迫IdentitiesOnly=yes。这迫使Vagrant只查看我们在亚马逊网络服务提供商的Vagrantfile中列出的私钥。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|499259|我在a+blog+post中写下了我们的经验。在某个时刻，它可能会变成一个拉取请求。|499260|entityMap|0|LINK|mutability|MUTABLE|url|http://www.benjaminoakes.com/2013/04/10/ssh-agent-forwarding-with-vagrant-aws/^0|M|B|28|2|2G|I|3Q|B|0|2|B|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|H|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

When we recently tried out the <code>vagrant-aws</code> plugin with Vagrant 1.1.5, we ran into an issue with SSH agent forwarding. It turned out that Vagrant was forcing <code>IdentitiesOnly=yes</code> without an option to change it to <code>no</code>. This forced Vagrant to only look at the private key we listed in the <code>Vagrantfile</code> for the AWS provider.

I wrote up our experiences in <a href="http://www.benjaminoakes.com/2013/04/10/ssh-agent-forwarding-with-vagrant-aws/" rel="nofollow">a blog post</a>. It may turn into a pull request at some point.

blocks|key|499308|text|除了将"config.ssh.forward_agent+=+true“添加到vagrant文件之外，还要确保主机计算机已设置为代理转发。Github为此提供了一个good+guide。(查看故障排除部分)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|499309|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/articles/using-ssh-agent-forwarding^0|2A|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

In addition to adding "config.ssh.forward_agent = true" to the vagrant file make sure the host computer is set up for agent forwarding. Github provides a <a href="https://help.github.com/articles/using-ssh-agent-forwarding" rel="noreferrer">good guide</a> for this. (Check out the troubleshooting section).

blocks|key|282597|text|我在1.4.3版本上使用了上面的回复，但在1.5版本上停止了工作。我现在必须运行ssh-add才能完全使用1.5。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|282598|现在，我将以下行添加到我的ansible配置脚本中。-+name:+Make+sure+ssk+keys+are+passed+to+guest.+++++++local_action:+command+ssh-add|282599|我还创建了我的设置要点：https://gist.github.com/KyleJamesWalker/9538912|282600|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/KyleJamesWalker/9538912^0|14|7|0|Q|2B|0|C|1B|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

I had this working with the above replies on 1.4.3, but stopped working on 1.5. I now have to run <code>ssh-add</code> to work fully with 1.5.

For now I add the following line to my ansible provisioning script.
<code>
 - name: Make sure ssk keys are passed to guest.
 local_action: command ssh-add
</code>

I've also created a gist of my setup: <a href="https://gist.github.com/KyleJamesWalker/9538912">https://gist.github.com/KyleJamesWalker/9538912</a>

blocks|key|282647|text|如果您使用的是Windows，Vagrant中的SSH转发在默认情况下无法正常工作(因为net-ssh中存在错误)。查看这个特定的Vagrant+bug报告：https://github.com/mitchellh/vagrant/issues/1735|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|282648|但是，有一个变通方法！只需通过VagrantFile中的简单配置脚本将本地SSH密钥自动复制到Vagrant+VM即可。下面是一个例子：https://github.com/mitchellh/vagrant/issues/1735#issuecomment-25640783|282649|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mitchellh/vagrant/issues/1735|1|https://github.com/mitchellh/vagrant/issues/1735#issuecomment-25640783^0|27|1C|0|0|1W|1Y|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you are on Windows, SSH Forwarding in Vagrant does not work properly by default (because of a bug in net-ssh). See this particular Vagrant bug report: <a href="https://github.com/mitchellh/vagrant/issues/1735">https://github.com/mitchellh/vagrant/issues/1735</a>

However, there is a workaround! Simply auto-copy your local SSH key to the Vagrant VM via a simple provisioning script in your VagrantFile. Here's an example:
<a href="https://github.com/mitchellh/vagrant/issues/1735#issuecomment-25640783">https://github.com/mitchellh/vagrant/issues/1735#issuecomment-25640783</a>

blocks|key|499423|text|确保VM不启动其自己的SSH代理。我的~/.profile里有这行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|499424|eval+`ssh-agent`|code-block|syntax|javascript|499425|删除后，SSH代理转发起作用了。|499426|entityMap^0|J|A|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Make sure that the VM does not launch its own SSH agent. I had this line in my <code>~/.profile</code>

<pre><code>eval `ssh-agent`
</code></pre>

After removing it, SSH agent forwarding worked.

blocks|key|499485|text|在Windows上，问题是Vagrant不知道如何与git-bash的ssh-agent通信。但是，它知道如何使用PuTTY's+Pageant。所以，只要Pageant正在运行并且已经加载了你的SSH，只要你已经设置了config.ssh.forward_agent，它就应该可以工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|499486|详情请参见this+comment。|offset|length|499487|如果您使用Pageant，则不再需要workaround+of+updating+the+Vagrantfile+to+copy+SSH+keys+on+Windows。|499488|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/hashicorp/vagrant/issues/1735#issuecomment-25640783|1|https://stackoverflow.com/a/24743876/25507^0|0|5|C|0|0|I|1U|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

On Windows, the problem is that Vagrant doesn't know how to communicate with git-bash's ssh-agent. It does, however, know how to use PuTTY's Pageant. So, as long as Pageant is running and has loaded your SSH key, and as long as you've set config.ssh.forward_agent, this should work.

See <a href="https://github.com/hashicorp/vagrant/issues/1735#issuecomment-25640783" rel="nofollow noreferrer">this comment</a> for details.

If you use Pageant, then the <a href="https://stackoverflow.com/a/24743876/25507">workaround of updating the Vagrantfile to copy SSH keys on Windows</a> is no longer necessary.

Rather than create a new SSH key pair on a vagrant box, I would like to re-use the key pair I have on my host machine, using <a href="http://www.unixwiz.net/techtips/ssh-agent-forwarding.html" rel="noreferrer">agent forwarding</a>. I've tried setting <a href="http://vagrantup.com/v1/docs/config/ssh/forward_agent.html" rel="noreferrer">config.ssh.forward_agent</a> to TRUE in the Vagrantfile, then rebooted the VM, and tried using:

<pre><code>vagrant ssh -- -A
</code></pre>

...but I'm still getting prompted for a password when I try to do a git checkout. Any idea what I'm missing?

How to use ssh agent forwarding with "vagrant ssh"?

虚拟机

Windows

我不想在流浪机器上创建新的SSH密钥对，而是使用重用我在主机上拥有的密钥对。我尝试在Vagrantfile中将设置为TRUE，然后重启虚拟机，并尝试使用：vagrant ssh -- -A...but当我尝试进行git结账时，仍然会收到输入密码的提示。知道我错过了什么吗？

问如何使用ssh代理转发与“流浪ssh"？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用ssh代理转发与“流浪ssh"？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用ssh代理转发与“流浪ssh"？
EN