netdev - SCTP connect() both ways

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

Date:	Mon, 9 Jun 2014 09:41:51 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: SCTP connect() both ways

When SCTP is used for protocols like M3UA it seems common
to configure both port numbers for a connection (typically
to the same value).

Rather than having one system call connect() and the other
listen(), both systems really want to try to establish the
connection by sending out INIT chunks.

The connection then gets established as soon as the second of the
two systems attempts to establish it.

However if the remote system responds with an ABORT (or maybe
an ICMP error is received) the Linux SCTP stack immediately
reports 'connect failed'.
For these sorts of connections it would be much better if the
received ABORT just increased the retry timer to large value.

Thoughts?

	David

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