Merge pull request #10288 from chrisroberts/e-win-pageant-doc
Add information on using pageant with ssh
This commit is contained in:
commit
56aa5860cb
|
@ -36,7 +36,7 @@ Welcome to your Vagrant-built virtual machine.
|
|||
Last login: Fri Jul 20 15:09:52 2018 from 10.0.2.2
|
||||
$ logout
|
||||
Connection to 127.0.0.1 closed.
|
||||
$
|
||||
$
|
||||
```
|
||||
|
||||
On multi-machine setups, you can login to each vm using the name as displayed
|
||||
|
@ -50,7 +50,7 @@ node1 running (virtualbox)
|
|||
node2 running (virtualbox)
|
||||
|
||||
This environment represents multiple VMs. The VMs are all listed
|
||||
above with their current state.
|
||||
above with their current state.
|
||||
$ vagrant ssh node1
|
||||
|
||||
Welcome to your Vagrant-built virtual machine.
|
||||
|
@ -63,18 +63,18 @@ Welcome to your Vagrant-built virtual machine.
|
|||
Last login: Fri Sep 14 06:23:18 2012 from 10.0.2.2
|
||||
vagrant@precise64:~$ logout
|
||||
Connection to 127.0.0.1 closed.
|
||||
$
|
||||
$
|
||||
```
|
||||
|
||||
On a system with machines running from different projects, you could use the id
|
||||
as listed in `vagrant global-status`
|
||||
|
||||
```bash
|
||||
$ vagrant global-status
|
||||
id name provider state directory
|
||||
$ vagrant global-status
|
||||
id name provider state directory
|
||||
-----------------------------------------------------------------------
|
||||
13759ff node1 virtualbox running /Users/user/vagrant/folder
|
||||
|
||||
13759ff node1 virtualbox running /Users/user/vagrant/folder
|
||||
|
||||
The above shows information about all known Vagrant environments
|
||||
on this machine. This data is cached and may not be completely
|
||||
up-to-date (use "vagrant global-status --prune" to prune invalid
|
||||
|
@ -87,7 +87,7 @@ Welcome to your Vagrant-built virtual machine.
|
|||
Last login: Fri Jul 20 15:19:36 2018 from 10.0.2.2
|
||||
vagrant@precise64:~$ logout
|
||||
Connection to 127.0.0.1 closed.
|
||||
$
|
||||
$
|
||||
```
|
||||
|
||||
If a `--` (two hyphens) are found on the command line, any arguments after
|
||||
|
@ -126,3 +126,15 @@ shell, and when the shell exits, all of the child processes also exit.
|
|||
To avoid this, you will need to detach the process from the shell. Please
|
||||
Google to learn how to do this for your shell. One method of doing this is
|
||||
the `nohup` command.
|
||||
|
||||
## Pageant on Windows
|
||||
|
||||
The SSH executable will not be able to access Pageant on Windows. While
|
||||
Vagrant is capable of accessing Pageant via internal libraries, the
|
||||
SSH executable does not have support for Pageant. This means keys
|
||||
from Pageant will not be available for forwarding when using the
|
||||
`vagrant ssh` command.
|
||||
|
||||
Third party programs exist to allow the SSH executable to access Pageant
|
||||
by creating a unix socket for the SSH executable to read. For more information
|
||||
please see [ssh-pageant](https://github.com/cuviper/ssh-pageant).
|
||||
|
|
Loading…
Reference in New Issue