The GUI client can be launched from the command line. This is useful for creating customized shortcuts, or other wrapper scripts (e.g., *.bat files).
The program is named SSHClient, and supports the following options:[179]
Reset all customizations made to the user interface (toolbars and menus). The client asks for confirmation before doing this.
Specify the remote username.
Specify the remote hostname (where the SSH server runs).
Specify the port number.
Start using the file-transfer window instead of the terminal window.
A profile settings file (*.ssh2) can also be specified as the last argument on the command line.
The GUI client immediately initiates an outgoing connection if any of the -u, -h, or -p options, or a profile settings file, are specified. If no remote hostname is given (either by the -h option or a profile settings file), then the client prompts for connection parameters, with any other supplied values as defaults. Otherwise, the client starts in an unconnected state and waits for outgoing connections to be initiated manually.
The precedence for settings is (from strongest to weakest):
Command-line options
A profile settings file specified on the command line
Default profile settings files: either default.ssh2 or defaultsftp.ssh2 (if the -f option is used)
Hardwired default settings, if the default profile settings files do not exist
The Tectia Client package also supplies a set of command-line programs, including ssh2, scp2, sftp2, and ssh-keygen2.[180] These programs are intended for scripting, and function almost exactly as they do for Unix implementations, except that they are aware of the Windows conventions for configuration file locations. In fact, ssh2 -h is an easy way to list the location of the configuration files for the client (in the user profile folder). The programs understand both Windows and Unix filename conventions using backslashes and (forward) slashes, respectively. Wildcards are case-insensitive, in accordance with Windows filesystem conventions.