SSH Communications Security
Previous Next Up [Contents] [Index]

    About This Document>>
    Introduction to SSH Secure Shell >>
    Configuring SSH Secure Shell >>
        Basic Configuration>>
        Subconfigurations
            Host-Specific Subconfiguration
            User-Specific Subconfiguration
        Configuring SSH Secure Shell for TCP Wrappers Support>>
        Configuring SSH2 for SSH1 Compatibility
        Forwarding>>
    Authentication >>
    Log Messages >>
    Using SSH Secure Shell >>
    Tool Syntax>>
    Technical Specifications >>

Subconfigurations

You can also specify configuration options in so-called subconfiguration files, which have the same basic format as the main configuration file. The process forked to handle the user's connection reads these files. They are read at run-time, so if they are modified, it is not necessary to restart the server process.

If parsing of the subconfiguration files fails, the connection is terminated (for host-specific configuration), or access denied (for user-specific configuration) by the server.

The subconfiguration files are divided into two categories: host-specific and user-specific.

Subconfiguration files are very flexible and because of that, dangerous if the logic of the files is not carefully planned. Note: Host-specific subconfiguration files are always read before the user-specific subconfiguration files. See the example file sshd2_config.example and the host-specific and user-specific files in /etc/ssh2/subconfig.

Host-Specific Subconfiguration

User-Specific Subconfiguration

Previous Next Up [Contents] [Index]


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

Copyright © 2003 SSH Communications Security Corp.
All rights reserved.
Copyright Notice