[TriLUG] Annoying daemon.log entries with ssh

Scott Lambdin lopaki at gmail.com
Wed Nov 14 13:19:29 EST 2007


I saw this out there in the ether.  Have your syslogging turned way up?

The first[1] step in the SSHv2 authentication is to request an
authentication with a method of "none". If the server requires no further
authentication then it must allow the "none" authentication to succeed,
otherwise it must reply with a list of authentications that the server
allows.

It's normal, but it's usually only logged at LogLevel VERBOSE so it doesn't
normally make it to the log files.



On 11/14/07, Joseph Mack NA3T <jmack at wm7d.net> wrote:
>
> On Wed, 14 Nov 2007, Tarus Balog wrote:
>
> > Nov 14 11:09:59 server1 sshd[3896]: Failed none for weather
> > from ::ffff:10.1.1.1 port 52059 ssh2
> > Nov 14 11:09:59 server1 sshd[3896]: Accepted publickey for weather
> > from ::ffff:10.1.1.1 port 52059 ssh2
> >
> > The "Failed" one ends up getting mailed to me every hour.
>
> does the failed one go to stderr and the accepted one go to
> stdout?
>
> if so do something like this at the end of the cron line
>
>    2>/dev/null
>
> Joe
>
> --
> Joseph Mack NA3T EME(B,D), FM05lw North Carolina
> jmack (at) wm7d (dot) net - azimuthal equidistant map
> generator at http://www.wm7d.net/azproj.shtml
> Homepage http://www.austintek.com/ It's GNU/Linux!
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>



More information about the TriLUG mailing list