SSH: Difference between revisions
No edit summary |
→Client: save configuration for VSCode with VirtualBox |
||
| Line 89: | Line 89: | ||
Installing a program like [http://projects.gnome.org/seahorse/ Seahorse] makes it trivially easy to manage your GnuPG encryption keys. Seahorse just makes it easier for you to do what you otherwise would accomplish with several commands. You can generate a private key; and add the public key to remote servers enabling you to login to those remote servers without using a password. | Installing a program like [http://projects.gnome.org/seahorse/ Seahorse] makes it trivially easy to manage your GnuPG encryption keys. Seahorse just makes it easier for you to do what you otherwise would accomplish with several commands. You can generate a private key; and add the public key to remote servers enabling you to login to those remote servers without using a password. | ||
=== VSCode and VirtualBox === | |||
When using VirtualBox to manage Linux VMs on your local Windows host, you can setup your SSH config file with a simple stanza to forward local connections on port 2222 to the SSH server on the VM like this. | |||
<syntaxhighlight lang="bash"> | |||
Host 127.0.0.1 | |||
HostName 127.0.0.1 | |||
User root | |||
Port 2222 | |||
IdentityFile C:/Users/greg/.ssh/id_ed25519 | |||
</syntaxhighlight> | |||
In this way, VSCode will be able to seamlessly connect to the VM, without prompting for a password every time. | |||
== Fingerprints == | == Fingerprints == | ||