linux-kernel - Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get SIGPIPE

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20160318.183230.1601751551897264970.davem@davemloft.net>
Date:	Fri, 18 Mar 2016 18:32:30 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	glider@...gle.com
Cc:	edumazet@...gle.com, rweikusat@...ileactivedefense.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get
 SIGPIPE

From: Alexander Potapenko <glider@...gle.com>
Date: Tue, 15 Mar 2016 10:03:44 +0100

> According to IEEE Std 1003.1, 2013, sending data to a SOCK_SEQPACKET
> socketpair with MSG_NOSIGNAL flag set must result in a SIGPIPE if the
> socket is no longer connected.
> 
> I used the following program to check the kernel behavior:
 ...
> Signed-off-by: Alexander Potapenko <glider@...gle.com>

In the final analysis I don't think we can do this.

Properly working programs will start to mysteriously receive
signals in this situation and fail.

I'm sorry but I think we're stuck with this behavior.