netdev - Re: Treason uncloaked / Broken peer again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090227.163105.240371624.davem@davemloft.net>
Date:	Fri, 27 Feb 2009 16:31:05 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	greg@...kko.com
Cc:	ilpo.jarvinen@...sinki.fi, herbert@...dor.apana.org.au,
	netdev@...r.kernel.org
Subject: Re: Treason uncloaked / Broken peer again

From: Greg Lindahl <greg@...kko.com>
Date: Fri, 27 Feb 2009 13:22:34 -0800

> On Thu, Feb 26, 2009 at 11:30:58AM +0200, Ilpo Järvinen wrote:
> 
> > Right, it's rather crude to have buggy kernel which sends past the 
> > receiver's advertized window, and then when it cannot cope the results of 
> > its own bug (and prints that message), put a blame on others who behave in 
> > a compliant way.
> 
> Well, perhaps we shouldn't have the message be "Broken peer" when the
> problem is often on the node printing the message? Maybe "Something's
> broken, might be me"?

As has been mentioned several times in this thread and others, we have
tweaked the message to be more reasonable and in particular it doesn't
say "broken peer" any more.
--
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