netdev - Re: [RFC 0/2] Account for duplicate ACKs with invalid SACK-blocks

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 for Android: free password hash cracker in your pocket

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

Message-ID: <52159063.5010000@fatooh.org>
Date:	Wed, 21 Aug 2013 21:15:31 -0700
From:	Corey Hickey <bugfood-ml@...ooh.org>
To:	David Miller <davem@...emloft.net>
CC:	christoph.paasch@...ouvain.be, eric.dumazet@...il.com,
	netdev@...r.kernel.org, kernel@...uxace.com,
	benjamin.hesmans@...ouvain.be
Subject: Re: [RFC 0/2] Account for duplicate ACKs with invalid SACK-blocks

On 2013-08-21 20:32, David Miller wrote:
> From: Christoph Paasch <christoph.paasch@...ouvain.be>
> Date: Mon, 19 Aug 2013 21:29:26 +0200
> 
>> There exist sequence-number rewriting middleboxes, who do not modify the 
>> sequence-number in the SACK-blocks.
> 
> These are bugs that the vendor's should fix, not something we should
> cater to at all.
> 
> I'm not applying patches like these, and I've rejected similar
> workarounds in the past 18 years, so this position is strong and
> consistent.
> 
> Sorry.

That's not terrible for me; we'll most likely be turning off SEQ
randomization on the FWSM, when we have time to make sure it doesn't
break anything (which it shouldn't).

-Corey
--
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