| | |
| ||
| ||
     |
Under Connection Profiles you can configure separate connection settings for each Secure Shell server you connect to. You can also configure several profiles for the same server, for example, with different user accounts.
To add a connection profile, click Add profile in the Connection Profiles page. Type a name for the profile and click OK. By default, the profile name is also used as the hostname of the server.
Newly created connection profiles will inherit the default values for authentication, ciphers, MACs, and advanced server settings defined under the General → Defaults page (Defining Default Settings). The values can be customized on the profile-specific tabbed pages.
Define the profile settings in the tabbed view as described in Defining Connection Settings, Defining Authentication, Defining Ciphers, Defining MACs, Defining Advanced Connection Settings, Defining Proxy Settings, Defining Tunneling (SSH Tectia Client), Defining Color Settings (SSH Tectia Client), Defining Terminal Settings (SSH Tectia Client), Defining File Transfer Settings (SSH Tectia Client), and Defining Favorite Folders (SSH Tectia Client).
If you have a lot of different servers you are connecting to, you can organize the connection profiles in folders. To add a folder for connection profiles, click Add folder in the Connection Profiles page. Type a name for the folder and click OK. You can now add connection profiles to the folder by selecting the folder and clicking Add profile. The profile will be created in the folder.
To move a profile to a different profile folder, select the profile from the list and click Move. Select the folder where you want to move the profile from the drop-down list and click OK.
To rename a connection profile or a profile folder, select a profile or a folder and click Rename. Type a new name and click OK.
To remove a connection profile or a profile folder, select a profile or a folder and click Delete. You will be asked for confirmation. Click OK to proceed with the deletion.
Note that removing a profile folder removes also all profiles in it.
On the Connection tab, you can define the protocol settings used in the connection. Any changed connection settings will take effect the next time you log in.
Type the name of the remote host computer you want to connect to using
this profile. If you specify * (an asterisk) as the hostname,
you will be prompted to type in the hostname when connecting.
Type the username you want to use when connecting to the remote
host computer. If you specify * (an asterisk) as the username, you will
be prompted to type in the username when connecting. If you specify
%USERNAME% (note the percent signs) as the username, it will
be replaced with the name of the current Windows user account upon
connecting.
Type the port number you want to use for the Secure Shell connection. The default port is 22.
![[Note]](images/note.gif) | Note |
|---|---|
A Secure Shell server program must be listening to the specified port on the remote host computer or the connection attempt will not succeed. If you are unsure which port the remote host computer is listening to, contact the system administrator of the remote host. |
Select the desired compression setting from the drop-down menu. Valid choices are zlib and none. Compression is disabled by default.
Use this drop-down list to select a profile for creating a nested tunnel.
On the Authentication tab, you can define the user authentication methods for the profile.
Select the Use Defaults check box to use the authentication methods defined on the Defaults page (Defining Authentication), or clear the check box to define a custom list of authentication methods.
To add a new authentication method to the list, click Add and select the method from the drop-down menu.
To remove an authentication method, select a method from the list and click Delete.
Use the arrow buttons to organize the preferred order of the authentication methods. The first method that is allowed by the Secure Shell server is used. Note that in some cases, the server may require several authentication methods to be passed before allowing login.
Possible methods for user authentication are the following:
Password: Use a password for authentication.
Public-key: Use public-key authentication. See also Defining User Authentication.
Keyboard-interactive: Keyboard-interactive is designed to allow the Secure Shell client to support several different types of authentication methods, including RSA SecurID, and PAM. For more information on keyboard-interactive, see User Authentication with Keyboard-Interactive.
GSSAPI: GSSAPI (Generic Security Service Application Programming Interface) is a common security service interface that allows different security mechanisms to be used via one interface. For more information on GSSAPI, see User Authentication with GSSAPI.
On the Ciphers tab, you can define the encryption algorithms used for the profile.
Select the Use Defaults check box to use the algorithms defined on the Defaults page (Defining Ciphers), or define a cipher list using the arrow buttons. The ciphers are tried in the order they are specified.
On the MACs tab, you can configure the message integrity algorithms used for the profile.
Select the Use Defaults check box to use the algorithms defined on the Defaults page (Defining MACs), or define a MAC list using the arrow buttons. The MACs are tried in the order they are specified.
On the Server tab, you can define advanced server connection settings for the profile.
Select the check box to use the values defined on the Defaults page (Defining Advanced Connection Settings) for the server connection settings.
This settings define the number of transport channels used by the Secure Shell connection. Using more than one transport may increase the throughput over low bandwidth connections. Currently, a value of 1 to 8 transports is supported. The default is 2 transports.
This setting specifies how long idle time (after all connection channels are closed) is allowed for a connection before automatically closing the connection. The default is 5 seconds. Setting a longer time allows the connection to the server to remain open even after a session (for example, GUI client) is closed. During this time, a new session to the server can be initiated without re-authentication. Setting the time to 0 (zero) terminates the connection immediately when the last channel to the server is closed.
Select the check box if you want to have the server banner message file (if it exists) visible to users before login.
On the Proxy tab, you can select proxy settings for the profile.
Select this option if you do not want to use a proxy.
Select this option to use the proxy rules defined in the General settings Proxy page (Defining Proxy Rules).
Click Add... to add a new proxy definition for this profile.
Select the Type of the rule. The type can be Direct, Socks4, Socks5, or Http.
For other types than direct, enter the proxy server Address and Port.
Tunneling, or port forwarding, is a way of forwarding otherwise unsecured TCP traffic through an encrypted Secure Shell tunnel. You can secure for example POP3, SMTP, and HTTP connections that would otherwise be unsecured.
| Note |
|---|---|
The client-server applications using the tunnel will carry out their own authentication procedures (if any) the same way they would without the encrypted tunnel. |
Tunneling settings for the connection profile are configured using the Tunneling tab. Any changed tunneling settings will take effect the next time you log in.
It is possible to define separately for each connection profile whether X11 and/or agent forwarding are enabled, or whether the general default forwarding settings are applied to the profile.
Select this option to make the profile follow the default settings for X11 and agent forwarding defined on the Defaults - Tunneling tab (Defining Default Tunneling Settings).
Select the checkbox to allow this connection profile to use X11 forwarding.
SSH Tectia Client can securely tunnel (forward) X11 graphic connections from the remote host computer to an X Windows server running on the local computer.
| Note |
|---|---|
A prerequisite for X11 tunneling is that you have an X emulator (such as eXceed or Reflection X) running in passive mode on the Windows computer. |
To tunnel (forward) X11 traffic, do the following:
Install an X server (X emulation) program on Windows (eXceed, Reflection X, or the like).
Start SSH Tectia Client.
Select the Tunneling tab of the Connection Profiles page and make sure that the Tunnel X11 connections check box is selected.
Save your settings for SSH Tectia Client.
Quit the client, start it again and log into the remote host.
Start the X server (X emulation) program.
To test the tunneling, run xterm or xclock from SSH Tectia Client.
For more information, see X11 Forwarding.
Select the check box to allow this connection profile to use agent forwarding on the client side.
In agent forwarding, Secure Shell connections and public-key authentication data are forwarded from one server to another without the user having to authenticate separately for each server.
For more information, see Agent Forwarding.
Local (outgoing) tunnels protect TCP connections that your local computer forwards from a specified local port to the specified port on the remote host computer you are connected to.
It is also possible to forward the connection beyond the remote host computer. However, the connection is encrypted only between the client (local computer) and the Secure Shell server.
Click the Local tunnels tab to edit outgoing tunnel definitions.
To add a new local tunnel, click Add. The Local Tunnel dialog box opens.
The following fields are used to define a local tunnel:
Type: Select the type of the tunnel from the drop-down list. Valid choices are TCP and FTP. If you are tunneling an FTP connection, set the tunnel type as FTP. For other protocols, set the tunnel type as TCP.
| Note |
|---|---|
If the Secure Shell server and the FTP server are located on different computers, FTP tunneling works only if FTP is set to run in passive mode. If the Secure Shell server and the FTP server are located on the same computer, tunneling works regardless of whether FTP is running in passive or active mode. For more information on tunneling FTP, see FTP Tunneling. |
Listen port: This is the number of the local port that the tunnel listens to, or captures.
| Note |
|---|---|
The protocol or application that you wish to create the tunnel for may have a fixed port number (for example 143 for IMAP) that it needs to use to connect successfully. Other protocols or applications may require an offset (for example 5900 for VNC) that you will have to take into an account. |
Allow local connections only: Select this option if you want to allow only local connections to be made. This means that other computers will not be able to use the tunnel created by you. By default, only local connections are allowed. This is the right choice for most situations. You should carefully consider the security implications if you decide to also allow outside connections.
Destination host: This field defines
the destination host for the tunneling. The default value is
localhost.
| Note |
|---|---|
The destination host is resolved by the Secure Shell server
after the Secure Shell connection has been established, so here
|
Destination port: The destination port defines the port that is used for the forwarded connection on the destination host.
To edit a tunnel definition, select a tunnel from the list and click Edit. The Local Tunnel dialog opens.
To delete a tunnel definition, select a tunnel from the list and click Delete to remove a tunnel. Note that the selected tunnel will be removed immediately, with no confirmation dialog.
For more information on local tunnels, see Local Tunnels.
Remote (incoming) tunnels protect TCP connections that the remote host forwards from a specified remote port to the specified port on your local computer.
Click the Remote tunnels tab to edit incoming tunnel definitions. Click Add... to open the Remote Tunnel dialog box.
The following fields are used to define a remote tunnel:
Type: Select the type of the tunnel from the drop-down list. Valid choices are TCP and FTP. For more information on FTP tunneling, see FTP Tunneling.
Listen port: The port that the tunnel listens to, or captures from the remote host computer.
| Note |
|---|---|
Privileged ports (below 1024) can be forwarded only when logging in with root privileges on the remote host computer. |
Destination host: This field defines the destination host for the port forwarding. The default value is localhost.
| Note |
|---|---|
Here localhost refers to your local computer. Also note that if the connection from the remote host computer is forwarded beyond your local computer, that connection is unsecured. |
Destination port: The destination port defines the port that is used for the forwarded connection on the destination host.
To edit a tunnel definition, select a tunnel from the list and click Edit. The Remote Tunnel dialog opens.
To delete a tunnel definition, select a tunnel from the list and click Delete to remove a tunnel. Note that the selected tunnel will be removed immediately, with no confirmation dialog.
For more information on remote tunnels, see Remote Tunnels.
The colors used in the SSH Tectia Client terminal window can be selected using the Colors page.
The color settings can be defined either globally or per profile. When colors are defined in SSH Tectia Client Global Settings, the Use Global Colors option is not available, but the color settings will affect all connection profiles. See Selecting Colors.
Use Global Colors: Select the Use Global Colors check box if you want to use the same color settings for each connection. If the check box is selected, you cannot specify different color settings for each connection profile (the other color settings are grayed out).
The text colors affect the terminal window background color and the color of text in both a connected window and a disconnected window.
Foreground: Select the desired foreground color from the drop-down menu. Foreground color is used for text in a window that has a connection to a remote host computer. You can select from sixteen colors. Black is the default foreground color.
Background: Select the desired background color from the drop-down menu. You can select from sixteen colors. White is the default background color.
Selection: Use the drop-down menu to select the color that is used as the background color when selecting text with the mouse. You can select from sixteen colors. Aqua is the default selection color.
Disconnected: Use the drop-down menu to select the color that is used as the foreground color in a terminal window that has no connection to a remote host computer. You can select from sixteen colors. Gray is the default foreground color for a disconnected terminal window.
Select the desired cursor color from the drop-down menu. You can select from sixteen colors. Navy is the default cursor color.
With ANSI control codes it is possible to change the color of text in a terminal window. With the ANSI Colors setting you can select to use this feature. Even if you disable ANSI colors, you can still select your favorite text and background colors to be used in the terminal window.
Enable ANSI Colors: Select this check box to allow ANSI colors to be used in the terminal window. By default, ANSI colors are selected.
By reversing the display colors you can quickly change the display from positive (dark on light) to negative (light on dark) to improve visibility.
Reverse Video: Select this check box to change the foreground color into background color and vice versa. This setting affects the whole terminal window when you click OK.
The settings used for the SSH Tectia Client terminal are configured using the Terminal tab. Keyboard mappings take effect when you start a new connection or reset the terminal.
User Defined Keymap File: With this option you can create additional keyboard shortcuts or modify the existing ones. The additional key mappings are saved into a separate file with the .sshmap file extension. The current keymap file is displayed in the text field.
You can modify the current key mappings by clicking Edit to open the Keymap Editor dialog.
If you have defined an alternative keymap settings file, you can load it by typing the path and file name in the text field, or by clicking on the button on the right-hand side of the text field. Clicking the button will open an Open dialog that allows you to locate an alternative keymap file.
Backspace sends Delete: Select the Backspace sends Delete check box if you want to map the Backspace key to the Delete operation.
Delete Sends Backspace: Select the Delete Sends Backspace check box if you want to map the Delete key to the Backspace operation.
Enter sends CR + LF: Select the Enter sends CR + LF check box if you want to map the Enter key to send the carriage return (CR) and line feed (LF) characters. Otherwise only the line feed character will be sent.
Lock Function Keys: Select the Lock Function Keys check box if you want to lock the function keys.
Line Wrap: Select the Line Wrap check box if you want the text lines to wrap at the terminal window edge. By default, line wrapping is on.
Use Alt as meta key (send Escape): Select the Use Alt as meta key (send Escape) check box if you want the Alt key to function as the meta key in the same way as the Escape key. If this option is selected, you can for example press the Alt+X key combination to simulate the Escape followed by X.
Keypad Mode: Select how you want the numeric keypad on the right-hand side of the regular keyboard to function.
Numeric Keypad: The keypad is used to type numbers.
Application Keypad: The keypad is used for application control (with the keypad keys functioning as cursor keys, Home, End, Page Up, Page Down, Insert and Delete).
Terminal answerback: Use this drop-down list to select the same terminal answerback mode that is used by the SSH Tectia Server related to the profile.
Euro character: Use this drop-down list to select the support mode for the euro character (€).
The supported options are Windows (where euro is mapped as 0x80) and ISO 8859-15 (euro mapped as 0xA4). Select the same character set that is used by the SSH Tectia Server related to the profile.
Note however that enabling the euro character support will disable the 8-bit terminal control codes.
The File Transfer tab affects which files are transferred using ASCII mode.
Detect Windows server from the version string: Secure Shell client and server exchange version strings when setting up the connection. Select this check box to automatically detect Windows servers and use the correct setting for them. For this feature to work correctly, the Windows server has to specify "windows" in its version string.
Unix: Select the Unix check box to use Unix compatible line breaks (LF).
Windows: Select the Windows check box to use Windows compatible line breaks (CRLF).
Ask before ASCII transfer: If you select this check box, the client will ask you to specify the server type before each ASCII file transfer.
In the Favorites Folders tab, you can create a list of commonly used remote directories. These favorites can then be easily selected from a drop-down menu in the file transfer window.
This list contains the favorite folders you have defined for the current connection profile. You can add, remove, and sort the favorites by using Add..., Delete, and the arrow buttons below the list.
If you are defining a remote favorite that is located on a Windows
Secure Shell server, the folder on the Windows server must be specified as
follows: /drive/folder/subfolder.
A valid favorite folder definition would be, for example:
/C/Documents and Settings/All Users/Desktop
| |
Copyright 
2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Contact Information
