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 >>
    Configuration >>
        Configuration Files >>
        Subconfigurations >>
        Enabling FIPS Mode
        Ciphers and MACs
        Compression
        Configuring Root Logins
        Restricting User Logins
        Subsystems
        Configuring ssh2 for ssh1 Compatibility
        Auditing >>
            Configuring Logging in sshd2
            Logging SFTP Transactions
            Log Facilities for sshd2_config
        Securing SSH Tectia Client and Server >>
    Authentication >>
    Application Tunneling >>
    Troubleshooting >>
    Man Pages
    Advanced Options >>
    Log Messages >>

Configuring Logging in sshd2

sshd2 logs to the facility specified with the configuration option SysLogFacility. If the option is not set, sshd2 logs to the AUTH facility.

For example, if you want sshd2 to log to the LOCAL1 facility, you need to add the following to your server's configuration (/etc/ssh2/sshd2_config):

SysLogFacility      LOCAL1

The possible facilities are listed in Section Log Facilities below.

You also need to modify syslog's configuration, so it knows where to put the log messages.

In /etc/syslog.conf (or equivalent):

local1.info         /var/log/sshd2

On some systems, this file may need to exist before syslog will write to it, so you may need to create it:

# touch /var/log/sshd2

If syslog accesses files with a non-root UID, for example logger, you need to change the ownership of the file to that user.

Remember to restart both sshd2 and syslogd after making changes to their configuration files.

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


 

 
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