SSH: Difference between revisions

From miki
Jump to navigation Jump to search
Line 39: Line 39:
<source lang=bash>
<source lang=bash>
Host myhost
Host myhost
ProxyCommand none # Otherwise setting in Host * would be taken
ProxyCommand none # Otherwise setting in Host * would be taken
Host myProxiedHost
ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p # Connect through proxy (see man ssh_config)
Host *
Host *
ProxyCommand /usr/local/bin/ssh-tunnel.pl -f - - %h %p
ProxyCommand /usr/local/bin/ssh-tunnel.pl -f - - %h %p # Proxy the connection using ssh-tunnel
</source>
</source>



Revision as of 09:47, 3 November 2009

Reference

On this Wiki:

Tips

ssh -F hostname                             # Find hostname in ~/.ssh/known_hosts (useful if HashKnowHosts enabled)
ssh -l -f ~/.ssh/known_hosts                # Print fingerprint of known host keys
ssh -Lport:host:hostport hostname sleep 60  # Forward port, and exit after 60s if no connection is made

Install

After installing ssh (client & server), you have to create an ssh-key:

ssh-keygen

Configuration

SSH can be configured through file ~/.ssh/config. See man ssh_config for more information. The format is as follows:

# Specific configuration options for host host1
Host host1
  Option1     parameter
  Option2     parameter

# General configuration options for all hosts. 
# Options in this section applies if same option was *not already specified* in a relevant host section above.
Host *
  Option1     parameter
  Option2     parameter

The value to use for each option is given by the first section that matches the host specification and that provides a value for that option. So section Host * should always be at the end of the file, since any subsequent section will be ignored.

ProxyCommand

Specify the proxy command used by ssh to deal with proxies. If a default command is specified in host *, it can be overridden in a specific host section (use ProxyCommand none to tell ssh that there is no proxies).

Host myhost
  ProxyCommand    none                                         # Otherwise setting in Host * would be taken
Host myProxiedHost
  ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p  # Connect through proxy (see man ssh_config)
Host *
  ProxyCommand    /usr/local/bin/ssh-tunnel.pl -f - - %h %p    # Proxy the connection using ssh-tunnel

Command-Line

Remote Command Execution

  • SSH allows to execute any command on remote SSH host. The syntax is
ssh -t SSH_HOST COMMAND
  • To execute a remote command on remote host and stay connected afterwards, use ssh -t, along with bash rcfile, like:
ssh -t SSH_HOST "bash --rcfile PATH_TO_RC_FILE"

Don't miss the quotes around the command. Bash will execute the commands in the rc file, and will open a session. Connection remains open because stdin/stdout is not closed. Option -t allows for connecting with current terminal. Without this option, there will be no terminal connection, so bash would run in batch mode (no prompt), and terminal features like tab completion or color would be missing.

  • Another solution is to force bash interactive mode:
ssh SSH_HOST "bash --rcfile PATH_TO_RC_FILE -i"

Since there is no terminal, bash goes by default in non-interactive mode. Interactive mode is forced with option -i, and so prompt will be printed, etc. But this is only a partial solution because there is still no terminal, ie. no color, no TAB auto-completion.

Port Forwarding

Here two drawings that illustrate very clearly the mechanisms of port forwarding in SSH.

First the case of direct port forwarding, where a port is opened for listening on the SSH Server, and forwarded to a host and port accessible to the client.

Ssh port forwarding direct.png

Then the case of reverse port forwarding, where a port is opened for listening on the SSH Client, and forwarded to a host and port accessible to the server.

Ssh port forwarding reverse.png