[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <396556a20806181239q30024b8bv551f76a890befb0e@mail.gmail.com>
Date: Wed, 18 Jun 2008 12:39:03 -0700
From: "Adam Langley" <agl@...erialviolet.org>
To: "David Miller" <davem@...emloft.net>
Cc: billfink@...dspring.com, netdev@...r.kernel.org
Subject: Re: [PATCH] Fix corrupt TCP packets when options space overflows with MD5SIG enabled (v2)
On Wed, Jun 18, 2008 at 1:52 AM, David Miller <davem@...emloft.net> wrote:
> It's pretty easy, depending upon the timestamp resolution, to
> end up with the original transmit and the retransmit having
> the same timetsamp value. So this suggestion in the RFC is
> I think not a complete solution.
I happen to have just (unintentionally) simulated this, i.e. a
situation where MD5 signed packets with SACKs were dropped by the
receiving host. The transmitting host keeps sending packets with SACKs
and they keep getting dropped: the connection stalled.
AGL
--
Adam Langley agl@...erialviolet.org http://www.imperialviolet.org
--
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