linux-kernel - Re: [PATCH] sctp: if backlog is 0, listening shall not be deactivated.

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: <20090114163729.3468d232@lxorguk.ukuu.org.uk>
Date:	Wed, 14 Jan 2009 16:37:29 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Vlad Yasevich <vladislav.yasevich@...com>
Cc:	Pierre Habouzit <pierre.habouzit@...ersec.com>,
	Wei Yongjun <yjwei@...fujitsu.com>,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sctp: if backlog is 0, listening shall not be
 deactivated.

> I will submit a requirest to change this behavior in the spec, but I am not
> terribly optimistic.  This has been specified for a very long time and there
> might be applications taking advantage of the ability to shut listing off.
> 
> At this time, let's leave this as is.  A well written application should specify
> the listen backlog anyway, otherwise it's depending on the "may" language in the
> Posix spec and will not get consistent behavior across different systems.

Seems fair enough.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/