[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080729164008.GR3820@mea-ext.zmailer.org>
Date: Tue, 29 Jul 2008 19:40:08 +0300
From: Matti Aarnio <matti.aarnio@...iler.org>
To: netdev@...r.kernel.org
Subject: Re: "MD5 Hash NOT expected but found" ..
On Tue, Jul 29, 2008 at 09:16:15AM -0700, Stephen Hemminger wrote:
> On Tue, 29 Jul 2008 19:04:30 +0300
> Matti Aarnio <matti.aarnio@...iler.org> wrote:
>
> > Dmesg reports following on 2.6.26-0.45.rc4.git2.fc10.x86_64
> >
> > MD5 Hash NOT expected but found (207.118.50.124, 4463)->(212.16.98.133, 25)
> > MD5 Hash NOT expected but found (207.118.50.124, 4463)->(212.16.98.133, 25)
> > MD5 Hash NOT expected but found (64.91.108.168, 3704)->(212.16.98.133, 25)
> > MD5 Hash NOT expected but found (64.91.108.168, 3704)->(212.16.98.133, 25)
...
>
> Somebody is trying to connect with MD5 option.
> This kernel message is too verbose for production systems.
Probably yes. I have seen those kernel messages less frequently than
once per day on average. "Rule of Least Confusion" does suggest that
unless this really reports about something being wrong, it should not
report it -- if it is generated because the coder was unsure of what
will happen, then the kernel needs more pacthing.
Current server uptime is 54 days, which means the kernel may have
already been patched somehow regarding this.
/Matti Aarnio
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists