BRIZ

Baud rate at which the communications device operates. This member can be an actual baud rate value, or one of the following indexes: 110, 19200, 300, 38400, 600, 56000, 1200, 57600, 2400, 115200, 4800, 128000, 9600, 256000, 14400

Lock Sound - enables of a sound signal at keyboard locking

Exit dialog on fail

Exit dialog - ask on exit

Auto CR/LF flag converts single CR or LF to CR/LF

Prefix text at begining of each dump line

If this member is 1, the CTS (clear-to-send) signal is monitored for output flow control. If this member is 1 and CTS is turned off, output is suspended until CTS is sent again.

Scale. Scale allows enlarge dialogs and frames. This setting apply only at moment of creation of GUI objects and can get anexpected result. Property SCALE= override this settings.

Use default font. By default, dialogs and frames using system font. You can set any font, installed in Your system. Property FONT= override this settings.

Locale string - Defines the locale (country and language) to be used when translating wide-character constants and string literals.
Examples:
French_Canada.1252
  French_Canada.ACP - Set code page to French Canada ANSI default
  French_Canada.OCP - Set code page to French Canada OEM default
  .1252 English_United States.1252

Number of columns on screen

Shutdown PC after closing of terminal.

• 0 - LOGOFF
• 1 - POWEROFF
• 2 - REBOOT
• 3 - SHUTDOWN
• 4 - FORCE_LOGOFF
• 5 - FORCE_POWEROFF
• 6 - FORCE_REBOOT
• 7 - FORCE_SHUTDOWN
• 8 - FORCEIFHUNG_LOGOFF
• 9 - FORCEIFHUNG_POWEROFF
• 10 - FORCEIFHUNG_REBOOT
• 11 - FORCEIFHUNG_SHUTDOWN
• 12 - LockWorkStation

Don't start a shell or command - will not attempt to run a shell or command after connecting to the remote server. You might want to use this option if you are only using the SSH connection for port forwarding, and your user account on the server does not have the ability to run a shell. This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell).

Don't allocate a pseudo-terminal - when connecting to a Unix system, most interactive shell sessions are run in a pseudo-terminal, which allows the Unix system to pretend it's talking to a real physical terminal device but allows the SSH server to catch all the data coming from that fake device and send it back to the client. Occasionally you might find you have a need to run a session not in a pseudo-terminal.

Enable compression - enables data compression in the SSH connection: data sent by the server is compressed before sending, and decompressed at the client end. Likewise, data sent from PC to the server is compressed first and the server decompresses it at the other end. This can help make the most of a low-bandwidth connection.

Attempt keyboard-interactive authentication - the SSH-2 equivalent of TIS authentication is called ‘keyboard-interactive’. It is a flexible authentication method using an arbitrary sequence of requests and responses; so it is not only useful for challenge/response mechanisms such as S/Key, but it can also be used for (for example) asking the user for a new password when the old one has expired.

SSH version - allows you to select whether you would like to use SSH protocol version 1 or version 2.

Max data before rekey - You might have a need to disable time-based rekeys completely for the same reasons that keepalives aren't always helpful. If you anticipate suffering a network dropout of several hours in the middle of an SSH connection, but were not actually planning to send data down that connection during those hours, then an attempted rekey in the middle of the dropout will probably cause the connection to be abandoned, whereas if rekeys are disabled then the connection should in principle survive (in the absence of interfering firewalls). For these purposes, rekeys have much the same properties as keepalives. (Except that rekeys have cryptographic value in themselves, so you should bear that in mind when deciding whether to turn them off.) Note, however, the the SSH server can still initiate rekeys. Max data before rekey specifies the amount of data (in bytes) that is permitted to flow in either direction before a rekey is initiated. If this is set to zero, then will not rekey due to transferred data. The SSH-2 protocol specification recommends a limit of at most 1 gigabyte. Disabling data-based rekeys entirely is a bad idea. The integrity, and to a lesser extent, confidentiality of the SSH-2 protocol depend in part on rekeys occuring before a 32-bit packet sequence number wraps around. Unlike time-based rekeys, data-based rekeys won't occur when the SSH connection is idle, so they shouldn't cause the same problems. The SSH-1 protocol, incidentally, has even weaker integrity protection than SSH-2 without rekeys.

Max minutes before rekey - if the session key negotiated at connection startup is used too much or for too long, it may become feasible to mount attacks against the SSH connection. Therefore, the SSH-2 protocol specifies that a new key exchange should take place every so often; this can be initiated by either the client or the server. While this renegotiation is taking place, no data can pass through the SSH connection, so it may appear to ‘freeze’. Usually the same algorithm is used as at the start of the connection, with a similar overhead. Max minutes before rekey specifies the amount of time that is allowed to elapse before a rekey is initiated. If this is set to zero, then will not rekey due to elapsed time. The SSH-2 protocol specification recommends a timeout of at most 60 minutes.

Attempt TIS or CryptoCard authentication - TIS and CryptoCard authentication are simple challenge/response forms of authentication available in SSH protocol version 1 only. You might use them if you were using S/Key one-time passwords, for example, or if you had a physical security token that generated responses to authentication challenges. With this switch enabled, then will attempt these forms of authentication if the server is willing to try them. You will be presented with a challenge string (which will be different every time) and must supply the correct response in order to log in. If your server supports this, you should talk to your system administrator about precisely what form these challenges and responses take.

Notify at starting of another session - shows Message box if more then one session and next flag is set