Re: SSH configuration problem
It should also be noted that OpenSSH 3.0.2 (the most current
stable version) does not log when tcp wrappers' hosts_access()
succeeds. I filed a bug and a patch for it,
http://bugzilla.mindrot.org/show_bug.cgi?id=65
>From Will Aoki on Saturday, 12 January, 2002:
>On Mon, Jan 07, 2002 at 08:00:02PM +0100, Luc MAIGNAN wrote:
>> Hi,
>>
>> my SSH connections don't go to the 'auth.log' file, but the sshd_config seems
>> to be good. What can happen ?
>Do you mean that you're not seeing *any* messages from sshd in the log
>file, or that sshd is logging, but that you only get messages about
>authentication, but not about connections being established - this:
>Jan 12 20:56:04 badkey sshd[14882]: Accepted password for waoki from 127.0.0.1 port 4075 ssh2
>instead of this:
>Jan 12 20:54:43 badkey sshd[14848]: Connection from 127.0.0.1 port 4074
>Jan 12 20:54:43 badkey sshd[14848]: Enabling compatibility mode for protocol 2.0
>Jan 12 20:54:43 badkey sshd[14848]: Failed none for waoki from 127.0.0.1 port 4074 ssh2
>Jan 12 20:54:46 badkey sshd[14848]: Accepted password for waoki from 127.0.0.1 port 4074 ssh2
>If so, you need to change a line in /etc/ssh/sshd_config from the
>default:
>LogLevel INFO
>to
>LogLevel VERBOSE
>and restart the ssh daemon.
>The name chosen for that configuration directive bothers me a bit,
>because it's too easily mistaken for syslog priority level - to someone
>who hasn't gone through the sshd manpage, the default configuration looks
>like it means "log at 'auth.info'", not "use verbosity level 'info'".
--
Joseph======================================================jap3003@ksu.edu
"If you really want to toggle [Internet Explorer] into secure mode, you
just need to click the little 'X" in the top right corner of the window."
--User dsb3 on www.slashdot.org. [Use Mozilla! www.mozilla.org.]
Reply to: