Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Saving Settings

When you have made changes to the user interface settings, an asterisk (*) is displayed on the SSH Tectia GUI title bar, after the name of the current settings file (for example: default*). This indicates that the changed settings are not yet permanent - they have not been saved yet.

If you want to make the changes permanent, you can save them for later use. Click the Save button on the toolbar, or select the File → Save Settings to save any changes you have made to your current settings.

The positions of the currently open terminal and file transfer windows can be saved separately with the File → Save Layout option. If you arrange your window positions and save the layout settings in the default settings file, the windows will be automatically positioned the way you prefer them when you next start the SSH Tectia Terminal.

Note that by default all of the windows will be opened at once. This can be changed on the Appearance page of the Settings dialog so that the defined windows are opened only when necessary when you open new terminal and file transfer windows. See Defining the Appearance.

If you spend a lot of effort specifying the settings, it is a good idea to create backup copies of the modified settings files (ssh-broker-config.xml, global.dat, and *.ssh2) and store them in a safe location. This way you will not have to create your personal settings again if your settings files are lost (for example because of a hardware failure).

Multiple Settings Files

You can save separate settings files for each remote host computer. This can be done by using the Profiles option. For more information on using profiles, see Defining Connection Profiles.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more