netdev - Re: [PATCH 3/4] [SCTP] Set assoc_id correctly during INIT collision.

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

Message-Id: <20070504.135545.77403988.davem@davemloft.net>
Date:	Fri, 04 May 2007 13:55:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	vladislav.yasevich@...com
Cc:	netdev@...r.kernel.org, lksctp-developers@...ts.sourceforge.net
Subject: Re: [PATCH 3/4] [SCTP] Set assoc_id correctly during INIT
 collision.

From: Vlad Yasevich <vladislav.yasevich@...com>
Date: Fri,  4 May 2007 16:44:18 -0400

> During the INIT/COOKIE-ACK collision cases, it's possible to get
> into a situation where the association id is not yet set at the time
> of the user event generation.  As a result, user events have an
> association id set to 0 which will confuse applications.
> 
> This happens if we hit case B of duplicate cookie processing.
> In the particular example found and provided by Oscar Isaula
> <Oscar.Isaula@...orola.com>, flow looks like this:
> A				B
> ---- INIT------->  (lost)
> 	    <---------INIT------
> ---- INIT-ACK--->
> 	    <------ Cookie ECHO
> 
> When the Cookie Echo is received, we end up trying to update the
> association that was created on A as a result of the (lost) INIT,
> but that association doesn't have the ID set yet.
> 
> Signed-off-by: Vlad Yasevich <vladislav.yasevich@...com>

Applied, thanks for fixing this up.
-
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