DetermineSet sshd to log to it's own file?

[Keith Clark]

I am trying to setup ssh to log to it's own log file and realized that the way it is implemented, I cannot guarantee that sshd is the only program that will log to the file.

The sshd_config man page states that the possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7. Let's say that I pick local6 and edit syslog.conf to send local6.debug to /var/adm/sshd.log.

What is to stop some other program from using the local6 facility? Nothing that I can see.
Is there any way to determine what is using the various facilities besides watching the log file?
Does anyone know of a way to ensure that sshd uses it's own log file?


I am using SSH Secure Shell 3.1.0

[Keith Clark]

Sorry, the subject should be "Set sshd to log to it's own file?"

[Sridhar Bhaskarla]

If at all anything could be done is through configure options and I did not see any such while compiling sshd.

So, it is not possible to do it. Only way is the way you are doing.

Also, all the SSHs prior to 3.4 are having a serious buffer overflow issue. Since it is publicly known now, bettter upgrade yours to 3.4.

-Sri