netdev - Re: TCP: orphans broken by RFC 2525 #2.17

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100926.181202.28824153.davem@davemloft.net>
Date:	Sun, 26 Sep 2010 18:12:02 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	w@....eu
Cc:	netdev@...r.kernel.org
Subject: Re: TCP: orphans broken by RFC 2525 #2.17

From: Willy Tarreau <w@....eu>
Date: Mon, 27 Sep 2010 01:25:30 +0200

> Agreed. But that's not a reason for killing outgoing data that is
> being sent when there are some data left in the rcv buffer.

What alternative notification to the peer do you suggest other than a
reset, then?  TCP gives us no other.

That's the thing, data integrity is full duplex, thus once it has been
compromised in one direction everything currently in flight must be
zapped.
--
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