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] [thread-next>] [day] [month] [year] [list]
Message-ID: <496E0A73.9030903@hp.com>
Date:	Wed, 14 Jan 2009 10:53:23 -0500
From:	Vlad Yasevich <vladislav.yasevich@...com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
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.

Alan Cox wrote:
>> SCTP API simply chooses to ignore the "may".  It is still fully compliant
>> with POSIX in this regard.
> 
> Linux chooses the interpretation that zero means one connection. Having a
> single protocol variant do different things is not nice because  a lot
> of code is designed to handle multiple address families and expect the
> same non address handling behaviour.
> 
> So while it may be able to claim posix compliance, its not Linux
> behaviour, and its relying on a specific interpretation of posix not
> being used by the OS.
> 
> At the very least the current behaviour of the SCTP code is plain rude.
> 

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.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ