From: Matti Aarnio <matti.aarnio@zmailer.org>
To: netdev@vger.kernel.org
Subject: Re: "MD5 Hash NOT expected but found" ..
Date: Tue, 29 Jul 2008 19:40:08 +0300 [thread overview]
Message-ID: <20080729164008.GR3820@mea-ext.zmailer.org> (raw)
In-Reply-To: <20080729091615.11595272@extreme>
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@zmailer.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
prev parent reply other threads:[~2008-07-29 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:04 "MD5 Hash NOT expected but found" Matti Aarnio
2008-07-29 16:16 ` Stephen Hemminger
2008-07-29 16:37 ` Adam Langley
2008-07-29 16:40 ` Matti Aarnio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080729164008.GR3820@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox