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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server >>
    Getting Started >>
        Location of Installed Files >>
            Configuration Files
            Key Files
            License File
        Starting and Stopping the Server >>
        Operation of the Server >>
        SSH Tectia Server (T) >>
        SSH Tectia Server (A) >>
        SSH Tectia Client >>
        Examples of Use
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Troubleshooting >>
    Man Pages
    Advanced Options >>
    Log Messages >>

Configuration Files

The system-wide configuration files consist of the following files:

  • Client configuration file: ssh2_config
  • Server daemon configuration file: sshd2_config
  • Certificate validation daemon configuration file: ssh_certd_config

The files contain keyword-value pairs, one per line. Lines starting with the hash character (#) as well as empty lines are interpreted as comments.

Example files ssh2_config.example, sshd2_config.example, and ssh_certd_config.example can be found in the same directory.

Users can have their own configuration files. These are stored in ~/.ssh2.

For detailed information about the options available in the configuration files, see the sshd2_config and ssh_certd_config man pages.

Subconfiguration files can also be specified in the main configuration file. See Section Subconfigurations for more information.

PreviousNextUp[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2010 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice

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