Differences between version 72 and predecessor to the previous major change of SSHNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 72 | Last edited on Wednesday, March 8, 2006 10:53:54 pm | by LawrenceDoliveiro | Revert |
| Older page: | version 71 | Last edited on Thursday, November 17, 2005 6:36:07 pm | by AlastairPorter | Revert |
@@ -53,8 +53,20 @@
Some ways to work around this:
* Add ''!StrictHostKeyChecking no'' to each stanza in your ssh_config(5). This will still produce a warning, but will connect without any input needed
* Add ''!UserKnownHostsFile ~/.ssh/known_hosts_foo'' to each ssh_config(5) stanza.
+Better technique: set up aliases for the different host/port combinations in your ssh_config file, e.g.
+
+ Host machine89
+ Hostkeyalias machine89
+ Host example.com
+ Port 8922
+ Host machine90
+ Hostkeyalias machine90
+ Host example.com
+ Port 9022
+
+The "Hostkeyalias" keyword specifies an alternative name (rather than the host name) to use for finding the host key in your known-hosts file, whereas the "Host" keyword is what you type on the command line instead of the host name. This means you can type "ssh machine89" instead of "ssh -p 8922 example.com" and "ssh machine90" instead of "ssh -p 9022 example.com". See the ssh_config(5) man page for other options you can put in your "Host" stanzas, including different usernames etc.
!!!Port Forwarding
[SSH] can forward ports across its encrypted tunnel. Using the following command,
