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


Chapter 4 Configuring Tectia Server

Tectia Server uses an XML-based configuration file ssh-server-config.xml that allows flexible implementation of real-life enterprise security policies.

The configuration file can be used to define settings with values that are different from the factory-set default values. When the configuration file has been created, the values of elements included in the file will override the default values of those elements. Any elements not included in the configuration file will use the hardcoded default values.

You can view the default values in the ssh-server-config-default.xml file that is stored in /etc/ssh2/ on Unix and in <INSTALLDIR>\Tectia Server\ on Windows. The default configuration file is not read by Tectia Server, but it shows the hardcoded system defaults.

The Tectia Server includes also an example file ssh-server-config-example.xml that contains a useful example configuration with explanations of the options. The example file is located in the same directory as the default configuration file.

On Windows, you can use the Tectia Server Configuration tool to edit the configuration (see Tectia Server Configuration Tool). The ssh-server-config.xml configuration file can also be edited with an XML editor or ASCII text editor directly in XML format (see Configuration File for Tectia Server).

After editing the configuration file, in most cases it is enough to reconfigure the server, but changing the listener ports or the FIPS-mode settings requires restarting the server. On Windows, reconfiguration happens when you click "Apply" or "OK". On Unix, to make Tectia Server re-read its configuration, you can use the ssh-server-ctl(8). For server restarting instructions, see Starting and Stopping the Server.

Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps