![\"SSH\"](\"images/colorbar_blue.png\") ![](\"images/logo_ssh_nega.png\"){kind=logo} |
![\"Home\"](\"images/home.gif\") ![](\"images/index.gif\") ![\"Prev\"](\"images/prev.gif\") ![\"Up\"](\"images/up.gif\") ![\"Next\"](\"images/next.gif\") |
Under Connection Profiles you can configure \nseparate connection settings for each Secure Shell server you connect to. \nYou can also configure several profiles for the same server, for example, \nwith different user accounts.
Click Test Connection to open a connection to the \nremote server. You need to connect to the server once in order to get the server's \nhost key. Tectia Client will prompt you to verify the received key. Check \nthat it is valid, preferably by calling the server's administrator, and save \nthe validated key. After this, the locally saved information on the key will \nbe used in the authentication process automatically.
To add a connection profile, click Add profile in \nthe Connection Profiles page. Enter a name for the profile \nand click OK. By default, the profile name is also used \nas the hostname of the server.
Newly created connection profiles will inherit the default values for \nauthentication, ciphers, MACs, KEXs, and advanced server settings defined under \nthe General → Defaults page \n(Defining Default Connection Settings). The values can be customized on the \nprofile-specific tabbed pages.
Define the profile settings in the tabbed view as described in\nDefining Connection Settings,\nDefining Authentication,\nDefining Ciphers,\nDefining MACs,\nDefining KEXs,\nDefining Server Connections,\n\nDefining Proxy Settings,\nDefining Tunneling,\nDefining Windows Settings,\nDefining Color Settings,\nDefining Terminal Settings,\nDefining File Transfer Settings, and\nDefining Favorite Folders.
You can organize the connection profiles in folders for each server \nyou are connecting to. To add a folder for connection profiles, click \nAdd folder in the Connection Profiles \npage. Enter a name for the folder and click OK. Add \nconnection profiles to the folder by selecting the folder and clicking \nAdd profile. The profile is created into the \nfolder.
To move a profile to a different profile folder, select the profile \nfrom the list and click Move. Select the folder where you \nwant to move the profile from the drop-down list and click \nOK.
To rename a connection profile or a profile folder, right-click on a profile \nor a folder name under Connection Profiles and click Rename. Type a new name, press Enter, and click \nOK or Apply.
To remove a connection profile or a profile folder, select a profile \nor a folder and click Delete. You will be asked for \nconfirmation. Click OK to proceed with the \ndeletion.
Note that removing a profile folder removes also all profiles in \nit.
To add a shortcut to the created profile on your desktop on Windows, \nclick Create Shortcut. When you double-click the icon, it \nwill directly open a connection to the host defined in the profile.
To add the created profile to your Windows taskbar, right-click the newly \ncreated desktop shortcut icon and then click Pin to Taskbar\non the shortcut menu. When you click the pinned Tectia SSH Terminal GUI taskbar button, a new Tectia SSH Terminal GUI \nwindow will appear, opening a Secure Shell connection with the settings defined in \nthe profile (hostname, port, user name etc.).
On the Connection tab, you can define the protocol \nsettings used in the connection. Any changed connection settings will take \neffect the next time you log in.
![\"Configuring](\"images/broker-connection.png\")
- Host Name
Specify the host name or the IP address of the remote host computer to \nwhich you want to connect with the profile.
- Port Number
Define the listen port on the Secure Shell server. The default SSH \nport number is 22. In case you know that the remote server uses another \nport, enter the number in the Port Number field.
![\"[Note]\"](\"images/note.gif\")
Note A Secure Shell server program must be listening to the specified \nport on the remote host computer or the connection attempt will not \nsucceed. If you are unsure which port the remote host computer is \nlistening to, contact the system administrator of the remote host.
- User Name
Select Use current Windows user name if the \nconnection should always be made using the currently logged in Windows user \nname. This is similar to defining
%USERNAME%(note the percent \nsigns) as the user name.%USERNAME%reads the actual user name \nfrom an environment variable.Select Specify user name and enter the user name, \nif you want to define the user name this profile will use when connecting \nto the remote host computer.
Select Prompt user for the user name if the user \nshould enter the user name manually every time when connecting.
Select Use the Default Connection's user name \nif you want to apply the generic user name defined in the \nGeneral - Default Connection settings.
- Advanced\n\n
In Compression, select the desired compression \nsetting from the drop-down menu. Valid choices are zlib \nand none. Compression is disabled by default.
In Tunnel using profile, use the drop-down list to \nselect a profile for creating a nested tunnel. The first tunnel will be \ncreated to the server defined in the current connection profile, and from \nthere, the second tunnel will be created to a host defined in the profile \nselected with the Tunnel using profile setting. By \ndefault, tunneling is disabled.
- Usage
This field shows information on where the defined profile is used.\n
On the Authentication tab, you can define the \nuser authentication methods for the profile.
![\"Configuring](\"images/broker-profile-auth.png\")
Select the Use Defaults check box to use the \nauthentication methods defined on the Default Connection \npage (Defining Authentication), or clear the check box to define a \ncustom list of authentication methods.
To add a new authentication method to the list, click \nAdd and select the method from the drop-down menu.
To remove an authentication method, select a method from the list and \nclick Delete.
Use the arrow buttons to organize the preferred order of the \nauthentication methods. The first method that is allowed by the Secure Shell \nserver is used. Note that in some cases, the server may require several \nauthentication methods to be passed before allowing login.
Possible methods for user authentication are:
Public-key: Use public-key \n authentication. See also Defining User Authentication. \n
Password: Use a password for \n authentication.
Keyboard-interactive: \n Keyboard-interactive is designed to allow the Secure Shell client to \n support several different types of authentication methods, including RSA \n SecurID, and PAM. For more information \n on keyboard-interactive, see User Authentication with Keyboard-Interactive. \n
GSSAPI: GSSAPI (Generic Security \n Service Application Programming Interface) is a common security service \n interface that allows different security mechanisms to be used via one \n interface. For more information on \n GSSAPI, see User Authentication with GSSAPI.
If you want to use the profile in non-interactive connections, you can \nselect to store a password with the profile in the Password \nAuthentication field.
Select Password to enter the actual password string. \n
Select Password file to enter a path to a file \ncontaining the password.
Select Password program to enter a path to a program \nor a script that outputs the password.
![\"[Caution]\"](\"images/caution.gif\")
Caution If the password is given using this option, it is extremely \n important that the
ssh-broker-config.xmlfile, \n the password file, or the program are not accessible by anyone else \n than the intended user.Note Any password given with the command-line options will override \n this setting.
In the GSSAPI Authentication field, by selecting the \nAllow Ticket Forwarding check box you can enable Tectia Client\nto allow forwarding the Kerberos ticket over several connections.
When using Public-Key Authentication, you can also define which\nkey types are used and how the keys are selected.
Key selection defines the policy Connection Broker \nuses when proposing user public keys to the server. Select the mode from the \ndrop-down list. The options are:
Try available public keys automatically \n (the default). With this policy, the client will try the keys in the \n following order:
Keys with public key available and private key without a \n passphrase (no user interaction)
Keys with public key available but private key behind a \n passphrase (require a passphrase query, provided the key is accepted by \n the server)
The rest of the keys, meaning keys that require a \n passphrase for the public key as well as the private key.
Prompt user to select the public key - \n with this policy, the Connection Broker prompts the user to select the key from a \n list of available keys. If authentication with the selected key \n fails, the client will prompt the user again to select another key.
Key types defines whether only plain public keys or \nonly certificates are tried during public-key authentication. Select the key \ntype from the drop-down list. The default is to try both plain public keys \nand certificates.
By selecting Issuer must match server certificate \nissuer, you can make the Connection Broker filter the user certificates \nthat will be included in the list presented to the user. The client-side \nuser certificates can be filtered according to their issuer name that is \ncompared to the certificate issuers requested or accepted by the server. By \ndefault, the filtering is not done. This option is useful when a user has \nseveral certificates with different access rights to the same server, for \nexample for a testing role and for an administrator role. The Connection Broker chooses \nthe relevant certificates that are applicable on the remote host, and the \nuser can choose the correct certificate from the short-listed ones.
To generate a public-key pair and to upload it to the remote server, \nclick the Public-Key Authentication Wizard button. For \ninstructions, see Using the Public-Key Authentication Wizard.
Enabled algorithms lists the public-key signature algorithms that\nare used for authenticating and signing the user's public key. The algorithms that will\nbe used are those that are configured for both Tectia Server and the Connection Broker. You can use the up\nand down arrow buttons to modify the order of the algorithms. To move an algorithm to\nthe Disabled algorithms list, select it and click the right arrow\nbutton.
Click OK to save the connection profile.
On Windows, you can use the Tectia Public-Key Authentication \nWizard to generate and to upload public-key pairs. The wizard will \ngenerate two key files, your private key and your public key.
The new private and public key will be stored on your local computer in \nthe %APPDATA%\\SSH\\UserKeys directory. The private key file has \nno file extension, and the public key has the same base file name as the \nprivate key, but with .pub as the file extension.
Select the Keys and Certificates page under \nUser authentication and click New \nKey to start the Public-Key Authentication Wizard.
![\"The](\"images/publickey-auth-wizard.png\")
Define the key properties and the required passphrase to protect \n your key pair; you will be requested to enter the passphrase always when \n using the keys to authenticate yourself.
- File Name \n
Type a unique name for the key file. Tectia Client \n suggest a name consisting of the user name and the host name.
- Comment
In this field you can write a short comment that \n describes the key pair. You can for example describe the connection the \n keys are used for. This field is not obligatory, but helps to identify the \n key later.
- Passphrase
Type a phrase that you have to enter when handling the \n key. This passphrase works in a similar way to a password and gives some \n protection for your private key.
Note In FIPS mode, due to a FIPS regulation which forbids exporting \nunencrypted private keys out of the FIPS module, it is not possible to \ngenerate user keys without a passphrase.
Make the passphrase difficult to guess. Use at least 8 characters, \n both letters and numbers. Any punctuation characters can be used as \n well.
Memorize the passphrase carefully, and do not write it down.
For connections where no user interaction is available, you can \n consider leaving the password empty.
- Retype passphrase
Type the passphrase again. This ensures that you have not \n made a typing error.
Click the Advanced Options, to define the type of \n the key to be generated and the key length to be different from the \n defaults. By default, Tectia Client generates a pair of 2048-bit RSA \n keys.
In the Key Properties fields, you can make the following selections:
- Key Type
Select the type of the key to be generated. Available options are DSA, RSA, ECDSA and Ed25519.
Note Ed25519 keys are not available in FIPS mode.
- Key Length
Select the length (complexity) of the key to be generated. Available \n options are:
DSA/RSA keys: 1024, 2048, 3072, 4096, 5120, 6144, 7168, 8192 bits
Note In FIPS mode (conforming to FIPS 186-3) the available DSA key lengths are limited to\n 1024, 2048 and 3072 bits.
ECDSA keys: 256, 384, 521 bits
Ed25519 keys: 512 bits
Larger keys of the same key type are more secure, but also slower to generate. A\n 256-bit ECDSA key and a 3072-bit DSA or RSA key provide equivalent security.
As soon as a new key has been generated, the Wizard proceeds to \nuploading the key to a remote server. In case you want to upload an existing \nkey to a remote server, select the key file in the Keys and Certificates \nview, and click Upload. The following dialog appears in \nboth cases:
![\"Uploading](\"images/publickey-upload-wizard.png\")
In the Upload Public Key view of the wizard, define \nthe remote host where to upload the key:
- Quick connect
Select this option to define the remote Host name and \nyour user name there. The default Secure Shell port is 22.
- Connection profile
Select a Connection profile from the drop-down list\nthat specifies the desired remote host and user name.
Click Upload to upload the key to the selected server. \nIf you are already connected to the remote server host, the key upload starts \nimmediately. If you are not connected, you will be prompted to authenticate \non the server (by default with password).
The public key will be uploaded to the default user home directory \n(%USERPROFILE%\\.ssh2 on Windows, $HOME/.ssh2 on Unix).
On the Ciphers tab, you can define the \nencryption algorithms used for the profile.
![\"Defining](\"images/broker-cipher.png\")
Select the Use Defaults check box to use the \nalgorithms defined on the Default Connection page \n(Defining Ciphers), or define a cipher list using the arrow \nbuttons. The ciphers are tried in the order they are specified.
Tectia proprietary algorithms are marked with \n(Tectia) and are operable with Tectia products only. They \ncorrespond to the algorithms that end with @ssh.com in the \nConnection Broker configuration file.
On the MACs tab, you can configure the \nmessage integrity algorithms used for the profile.
![\"Defining](\"images/broker-mac.png\")
Select the Use Defaults check box to use the \nalgorithms defined on the Default Connection page \n(Defining MACs), or define a MAC list using the arrow \nbuttons. The MACs are tried in the order they are specified.
Tectia proprietary algorithms are marked with \n(Tectia) and are operable with Tectia products only. They \ncorrespond to the algorithms that end with @ssh.com in the \nConnection Broker configuration file.
On the KEXs tab, you can configure the \nkey exchange methods used for the profile.
![\"Defining](\"images/broker-kex.png\")
Select the Use Defaults check box to use the \nmethods defined on the Default Connection page \n(Defining KEXs), or define a KEX list using the arrow \nbuttons. The KEXs are tried in the order they are specified.
Tectia proprietary algorithms are marked with \n(Tectia) and are operable with Tectia products \nonly. They correspond to the algorithms that end with @ssh.com in \nthe Connection Broker configuration file.
On the Server tab, you can define advanced \nserver connection settings for the profile.
![\"Defining](\"images/broker-profile-server.png\")
- Use Defaults
Select the check box to use the values defined on the \nDefault Connection page (Defining Server Connections) for the \nserver connection settings.
- Idle timeout
Specify how long idle time (after all connection \nchannels are closed) is allowed for a connection before automatically \nclosing the connection. The default is 5 seconds. Setting a longer time \nallows the connection to the server to remain open even after a session (for \nexample, Tectia SSH Terminal GUI) is closed. During this time, a new session to the \nserver can be initiated without re-authentication. Setting the time to 0 \n(zero) terminates the connection immediately when the last channel to the \nserver is closed.
- TCP connection timeout
Specify for how long a TCP connection will be attempted to a Secure \nShell server. Define the timeout in seconds. After the defined time the TCP \nconnection will be released in case the remote server is down or unreachable. \nSetting the value as 0 (zero) means that the default system TCP timeout will \nbe used.
- Keepalive interval
Specify an interval (in seconds) for sending keepalive messages to a \nSecure Shell server. The default is 0, meaning that no keepalive messages \nare sent.
- Exclusive connection
Select this check box if you want that the profile always opens a new \nconnection, instead of reusing a currently open connection.
- Show server banner
Select the check box if you want to have the server banner message \nfile (if it exists) visible to users before login.
- Enabled Hostkey Algorithms
This list shows the host key signature algorithms used for server authentication\nwith host keys or certificates. The algorithms that will be used are those that are\ndefined in both Tectia Server and Connection Broker configuration files. This way the use of only certain\nalgorithms, such as SHA-2, can be enforced by the server.
The host key algorithms are tried in the order they are specified, with one\nexception: If a host key of a server already exists in the host key store of the\nclient, its algorithm is preferred. You can use the up and down arrow buttons to\nmodify the order of the algorithms.
- Disabled Hostkey Algorithms
The host key algorithms listed here are not used for server authentication. To\ndisable a host key algorithm, select it in the Enabled Hostkey\nAlgorithms list and click the right arrow button.
On the Proxy tab, you can select proxy settings for \nthe profile.
![\"Defining](\"images/broker-proxy.png\")
- No proxy
Select this option if you do not want to use a proxy.
- Use proxy rules
Select this option to use the proxy rules defined in the \nGeneral settings Proxy Rules page \n(Defining Proxy Rules).
- Specify a proxy for this profile only
Click Add to add a new proxy definition for this \nprofile.
Select the Type of the rule. The type can be \nDirect, Socks4, \nSocks5, or Http.
For other types than direct, enter the address of the proxy \nServer and Port.
![\"Defining](\"images/broker-add-proxy-profile.png\")
Tunneling, or port forwarding, is a way of forwarding otherwise unsecured \nTCP traffic through an encrypted Secure Shell connection (tunnel). You can secure for \nexample POP3, SMTP, and HTTP connections that would otherwise be \nunsecured.
The tunneling settings for the connection profile are configured using the \nTunneling tab. Any changed tunneling settings will take \neffect the next time you log in.
![\"Defining](\"images/broker-tunneling.png\")
| Note |
|---|---|
The client-server applications using the tunnel will carry out their \nown authentication procedures (if any) the same way they would without the \nencrypted tunnel. |
It is possible to define separately for each connection profile \nwhether X11 and/or agent forwarding are enabled, or whether the general \ndefault forwarding settings are applied to the profile.
- Use Defaults
Select this option to make the profile follow the default settings for \nX11 and agent forwarding defined on the \nDefaults - Tunneling tab \n(Defining Default Tunneling Settings). \n
- Tunnel X11 connections
To allow X11 forwarding for this connection profile, select this check box.
Tectia Client can securely tunnel (forward) X11 graphic connections from the \nremote host computer to an X Windows server running on the local computer. \n
Note A prerequisite for X11 tunneling is that you have an X emulator \n(such as eXceed or Reflection X) running in passive mode on the Windows \ncomputer.
To tunnel (forward) X11 traffic, do the following actions:
Install an X server (X emulation) program on Windows \n(eXceed, Reflection X, or the like).
Start Tectia Client.
Select the Tunneling tab of the \nConnection Profiles page and make sure that the Tunnel X11 \nconnections check box is selected.
Save your settings for Tectia Client. \n
Restart Tectia Client and log into the remote host. \n
Start the X server (X emulation) program. \n
To test the tunneling, run xterm or xclock from \nTectia Client.
For more information, see X11 Forwarding.
- Allow Agent Forwarding
To allow agent forwarding on the client side for this connection profile, \nselect this check box.
In agent forwarding, Secure Shell connections and public-key \nauthentication data are forwarded from one server to another without the \nuser having to authenticate separately for each server.
For more information, see Agent Forwarding.
There are two types of tunnels that can be defined for application \ntunneling, local (outgoing) tunnels and remote (incoming) tunnels.
Local tunnels protect TCP connections that your local \ncomputer forwards from a specified local port to a specified port on the \nremote host computer you are connected to. It is also possible to forward \nthe connection beyond the remote host computer, but the connection is \nencrypted only between Tectia Client and Tectia Server.
Remote tunnels protect TCP connections that a remote host \nforwards from a specified remote port to a specified port on your local \ncomputer.
To edit local tunnel definitions, click the Local \ntunnels tab.
To add a new local tunnel, click Add. The \nLocal Tunnel dialog box opens.
![\"Defining](\"images/broker-tunneling-out.png\")
The following fields are used to define a local tunnel:
Type: Select the type of the tunnel from \nthe drop-down list. Valid choices are TCP and FTP. If you are tunneling an \nFTP connection, set the tunnel type as FTP. For other protocols, set the \ntunnel type as TCP.
Note If the Secure Shell server and the FTP server are located on \ndifferent computers, FTP tunneling works only if FTP is set to run in \npassive mode. If the Secure Shell server and the FTP server are located on \nthe same computer, tunneling works regardless of whether FTP is running in \npassive or active mode. \nFor more information on FTP tunneling, see Non-Transparent FTP Tunneling.\n
Listen port: This is the number of the \nlocal port which the tunnel listens to or captures.
Note The protocol or application that you wish to create the tunnel for \nmay have a fixed port number (for example 143 for IMAP) that it needs to \nuse to connect successfully. Other protocols or applications may require \nan offset (for example 5900 for VNC) that you will have to take into an \naccount.
Allow local connections only: Select \nthis option if you want to allow only local connections to be made. This \nmeans that other computers will not be able to use the tunnel created by \nyou. By default, only local connections are allowed. This is the right \nchoice for most situations.
Consider the security implications carefully if you decide to also \nallow outside connections.
Destination host: This field defines \nthe destination host for the tunneling. The default value is \n
localhost.Note The destination host is resolved by the Secure Shell server, \nso here
localhostrefers to the Secure Shell server host you are \nconnecting to.Destination port: The destination port \ndefines the port that is used for the forwarded connection on the \ndestination host.
To edit a tunnel definition, select a tunnel from the list and click \nEdit. The Local Tunnel dialog \nopens.
To delete a tunnel definition, select a tunnel from the list and click \nDelete to remove a tunnel. Note that the selected tunnel \nwill be removed immediately, with no confirmation dialog.
For more information on local tunnels, see \nLocal Tunnels.
Remote (incoming) tunnels protect TCP connections that the remote host forwards \nfrom a specified remote port to the specified port on your local computer. \n
Click the Remote tunnels tab to edit incoming \ntunnel definitions. Click Add to open the \nRemote Tunnel dialog box.
![\"Defining](\"images/broker-tunneling-in.png\")
The following fields are used to define a remote tunnel:
Type: Select the type of the tunnel \nfrom the drop-down list. Valid choices are TCP and FTP. \nFor more information on FTP tunneling, see Non-Transparent FTP Tunneling.\n
Listen port: Enter the port that the tunnel \nlistens to or captures from the remote host computer.
Note Privileged ports (below 1024) can be forwarded only when logging in \nwith root privileges on the remote host computer.
Destination host: Define \nthe destination host for the port forwarding. The default value is \nlocalhost.
Note Here localhost refers to your local computer. Also note that if the \nconnection from the remote host computer is forwarded beyond your local \ncomputer, that connection is unsecured.
Destination port: Define the port that is \nused for the forwarded connection on the destination host. \n
To edit a tunnel definition, select a tunnel from the list and click \nEdit. The Remote Tunnel dialog \nopens.
To delete a tunnel definition, select a tunnel from the list and click \nDelete to remove a tunnel. Note that the selected tunnel \nwill be removed immediately, with no confirmation dialog.
For more information on remote tunnels, see \nRemote Tunnels.
The type of the Tectia window that is opened initially is configured using \nthe Windows tab. The selected GUI version, \nTectia SSH Terminal GUI or Tectia Secure File Transfer GUI,\nwill be opened first when this profile is accessed.
![\"Defining](\"images/broker-profile-window.png\")
| Note |
|---|---|
When a profile is added from the Tectia Connections Configuration GUI using the Add \nProfile option, the initial window type of the new profile is \nautomatically set to be the same as in the current GUI view. |
The colors used in the Tectia SSH Terminal GUI can be selected using the \nColors page.
The color settings can be defined either globally or per profile. When \ncolors are defined in Tectia terminal Global Settings, the Use Global \nColors option is not available, but the color settings will affect \nall connection profiles. See Selecting Colors.
![\"Defining](\"images/broker-colors.png\")
Use Global Colors: Select this check box if you \nwant to apply the global color settings to this profile. When this check box \nis selected, you cannot modify the color settings.
- Text Colors
The text colors affect the terminal window background color and the \ncolor of text in both a connected window and a disconnected window. \n
Foreground: Select the desired \nforeground color from the drop-down menu. Foreground color is used for \ntext in a window that has a connection to a remote host computer. You can \nselect from sixteen colors. Black is the default foreground color. \n
Background: Select the desired \nbackground color from the drop-down menu. You can select from sixteen \ncolors. White is the default background color.
Selection: Select the desired \nbackground color for mouse-selected texts from the drop-down menu.\nYou can select from sixteen colors. Aquamarine is the default \nselection color.
Disconnected: Select the desired \nforeground color for terminal windows that have no connection to a remote \nhost computer. You can select from sixteen colors. Gray is the default \nforeground color for a disconnected terminal window.
- Cursor Color
Select the desired cursor color from the drop-down menu. You can \nselect from sixteen colors. Navy is the default cursor color.
- ANSI Colors
With ANSI control codes it is possible to change the color of text \nin a terminal window. With the ANSI Colors setting you can select to use \nthis feature. Even if you disable ANSI colors, you can still select your \nfavorite text and background colors to be used in the terminal window. \n
Select the Enable ANSI Colors check \nbox to allow ANSI colors to be used in the terminal window. By default, \nANSI colors are selected.
- Reverse Colors
By reversing the display colors you can quickly change the display \nfrom positive (dark on light) to negative (light on dark) to improve \nvisibility.
Select the Reverse Video check box to \nchange the foreground color into background color and vice versa. This \nsetting affects the whole terminal window when you click \nOK.
The settings used for the Tectia Client terminal are configured using \nthe Terminal tab. Keyboard mappings take effect when you \nstart a new connection or reset the terminal.
![\"Defining](\"images/broker-keyboard.png\")
- User Defined Keymap File
Use this option to create additional keyboard shortcuts or to modify \nthe existing ones. The additional key mappings are saved into a separate text\nfile with the
.sshmapfile extension. The current keymap file \nis displayed in the text field.If you have defined an alternative keymap settings file, you can load \nit by typing the path and file name in the text field, or by clicking \nBrowse. Clicking Browse will open an \nOpen dialog box that allows you to locate an alternative \nkeymap file.
You can modify the current key mappings and add new ones by clicking\n Edit. Clicking Edit will open the \n Tectia Keymap Editor, where you can create a new key \n mapping by clicking Add. Clicking Add \n will open the Tectia Shortcut dialog box.
To define a keyboard shortcut, on the Function\ndrop-down list, select the function you want to map a key to. Depending on\nthe function, you may further define it using an additional text box or \ndrop-down list that appears when you select a function. In the text box in \nthe lower left of the dialog box, press the key or key combination you \nwant to map to the function.
To use the new key mapping, restart Tectia Client and reconnect to the server \n using the same connection profile for which you made the mapping. Notice that \n the key mapping only applies to this specific connection profile.
- Predefined Keyboard Inputs
Select the Backspace sends Delete check \n box if you want to map the Backspace key to the Delete operation. \n
Select the Delete Sends Backspace check \n box if you want to map the Delete key to the Backspace operation. \n
Select the Enter sends CR + LF check \n box if you want to map the Enter key to send the carriage return (CR) and \n line feed (LF) characters. Otherwise only the line feed character will be \n sent.
Select the Lock Function Keys check box \n if you want to lock the function keys.
Select the Line Wrap check box if you \n want the text lines to wrap at the terminal window edge. By default, line \n wrapping is on.
Select the Use Alt as \n meta key (send Escape) check box if you want the Alt key to \n function as the meta key in the same way as the Escape key. If this option \n is selected, you can for example press the Alt+X key combination to \n simulate the Escape followed by X.
- Keypad Mode
Select how you want the numeric keypad on the right-hand \nside of the regular keyboard to function.
Select Numeric Keypad to use the keypad to enter\nnumbers.
Select Application Keypad to use the keypad for \napplication control (with the keypad keys functioning as cursor keys, Home, \nEnd, Page Up, Page Down, Insert and Delete).
- Terminal answerback\n
Use the Terminal answerback drop-down \nlist to select the same terminal answerback mode that is used by the Tectia Server \nrelated to the profile.
- Euro character\n
Use the Euro character drop-down list to \nselect the support mode for the euro character (€).
The supported options are Windows (where euro is mapped as 0x80) and ISO \n8859-15 (euro mapped as 0xA4). Select the same character set that is used by the \nTectia Server related to the profile.
Note however that enabling the euro character support will disable the \n8-bit terminal control codes.
![\"Adding](\"images/broker-keymap.png\")
The File Transfer tab defines which files are \ntransferred using ASCII mode and which newline conventions are applied.
![\"Defining](\"images/broker-filetransfer.png\")
- ASCII transfer with old servers
Detect Windows server from the version string: \nSecure Shell client and server exchange version strings when setting up the \nconnection. Select this check box to automatically detect Windows servers \nand use the correct setting for them. For this feature to work correctly, \nthe Windows server has to specify \"windows\" in its version string.
Select the Unix check box to use \nUnix compatible line breaks (LF).
Select the Windows check box \nto use Windows compatible line breaks (CRLF).
Select the Ask before ASCII transfer check box\nto make Tectia Client ask you to specify the server type \nbefore each ASCII file transfer.
In the Favorites Folders tab, you can create a list \nof commonly used remote directories. These favorites can then be easily \nselected from a drop-down menu in the file transfer window.
![\"Defining](\"images/broker-favorites.png\")
- Favorite Folders
This list contains the favorite folders you have defined for \nthe current connection profile. You can add, remove, and sort the favorites \nby using Add, Delete, and the arrow \nbuttons below the list.
If you are defining a remote favorite that is located on a Windows \nSecure Shell server, the folder on the Windows server must be specified as \nfollows:
/drive/folder/subfolder.A valid favorite folder definition would be, for example:
/C/Documents and Settings/All Users/Desktop
- Home Folder
In the Home Folder field you can enter the \ndirectory where any new SFTP connections associated with this profile will \nstart. If you leave the field empty, new connections will use the remote \nhome folder that has been specified for your user account on the remote host \ncomputer.
| |
\n Copyright ![](\"images/copyright.gif\")
2020 SSH Communications Security Corporation
\n This software is protected by international copyright laws. All rights reserved.
Contact Information