Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH Tectia

Using the Command-Line Client

To connect to a remote host using the command-line client:

  1. Run the sshg3 Secure Shell client. The basic command syntax is the following:

    $ sshg3 user@host#port
    

    In the command, user is your username on the server, host is the domain name or IP address of the server host, and port is the port where the Secure Shell server is running on. The default port for Secure Shell connections is 22.

    If you have defined connection profiles in the ssh-broker-config.xml file, you can also connect by using the name of the connection profile:

    $ sshg3 profile1
    

    In this case, the settings defined in the profile (hostname, port, username etc.) are used for the connection. For instructions on creating and editing the connection profiles, see the section called “The profiles Element”.

    For more information on the command-line commands and options, see Appendix A.

  2. When you connect to a remote server (using server public-key authentication), the server host will provide your local computer with its host public key. The host key identifies the server host.

    SSH Tectia Client checks if this key is already stored in your own host key directory. If not, the host key directory common to all users on your computer is checked next.

    If the host key is not found, you are asked to verify it.

    After verifying the key, you can select whether to cancel the connection, to proceed and to save the key, or to proceed without saving the key.

    For more information on server authentication, see Server Authentication with Public Keys.

  3. You will be prompted to authenticate yourself to the server. The required authentication method(s) depends on the server settings.

    After you have completed the authentication, you are logged in to the server.

===AUTO_SCHEMA_MARKUP===