[Contents] [Index]

About This Document >>     Installing SSH Tectia Server >>     Getting Started >>         Location of Installed Files >>         Starting and Stopping the Server >>         Operation of the Server >>         SSH Tectia Server (T) >>         SSH Tectia Server (A) >>         SSH Tectia Client >>             Using the Client (ssh2)             Using Secure Copy (scp2)             Using Secure File Transfer (sftp2)             Using Authentication Agent (ssh-agent2, ssh-add2)         Examples of Use     Configuration >>     Authentication >>     Application Tunneling >>     Troubleshooting >>     Man Pages     Advanced Options >>     Log Messages >>

Using the Client (ssh2)

The basic Secure Shell client program is called ssh2.

ssh2 can be used either to initiate an interactive session, resembling rlogin, or to execute a command in a way similar to the rsh command.

The Secure Shell client connects to the server on port 22, which is a well-known port for Secure Shell.

Starting the Client

The syntax of ssh2 is very simple:

ssh [options] hostname [command]

The most common usage is to establish an interactive session to a remote host. This can be done simply by typing ssh hostname.domain. A real-world example could be ssh root@somehost.ssh.com. The user ID to be used can also be specified with the -l option, for example ssh -l root somehost.ssh.com.

Note: As shown in the above example, in the normal case, you do not have to type ssh2. The installation process creates a symbolic link, ssh, that points to the actual ssh2 executable. If Secure Shell 1.x was installed before SSH Tectia, you have to type ssh1 to run the Secure Shell 1.x client.

Client Configuration File and Command-Line Options

ssh2 reads configuration data from /etc/ssh2/ssh2_config and from $HOME/.ssh2/ssh2_config (or the file specified with the -F option on the command line). The last obtained value will be used.

The file contains keyword-value pairs, one per line. Lines starting with the hash character (#) as well as empty lines are interpreted as comments.

For detailed information about the options available in the configuration file and on the command line, please refer to the ssh2_config and ssh2 man pages.