netdev - [QUESTION] AF_UNIX connect behavior when listener backlog=0

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

Message-ID: <20181023163141.a6nn5pua4o4zndde@shells.gnugeneration.com>
Date:   Tue, 23 Oct 2018 09:31:41 -0700
From:   Vito Caputo <vcaputo@...garu.com>
To:     linux-kernel <linux-kernel@...r.kernel.org>
Cc:     netdev@...r.kernel.org
Subject: [QUESTION] AF_UNIX connect behavior when listener backlog=0

The current implementation of AF_UNIX sockets immediately establishes a
new connection even when the backlog on the listener is zero.

Wouldn't it make more sense for connects to become synchronous with
accept when the listener is configured with a backlog of zero?

That way connects can be reliably refused from the listener side via
e.g. closing the listener instead of accepting the connect.

I'm not subscribed to netdev, so please take care to include me in any
replies on that list.

Regards,
Vito Caputo