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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 1 May 2014 16:00:49 -0700 From: Andy Lutomirski <luto@...capital.net> To: Al Viro <viro@...iv.linux.org.uk> Cc: Linux FS Devel <linux-fsdevel@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Network Development <netdev@...r.kernel.org> Subject: Re: Connecting to sockets on MNT_READONLY mounts? On Thu, May 1, 2014 at 3:34 PM, Al Viro <viro@...iv.linux.org.uk> wrote: > On Thu, May 01, 2014 at 03:20:00PM -0700, Andy Lutomirski wrote: >> Is it supposed to work? > > Why the hell not? Same as opening a device node on r/o filesystem for > write, or doing the same with FIFO. You can't bind a socket on a read-only fs, so I thought it was a fair question. I'll write a patch to add MS_NOIPCCONNECT and MNT_NOIPCCONNECT to block connect on unix sockets and open on fifos. This will be useful for sandboxes that want to prevent sandboxed programs from accessing undesirable parts of the outside world. --Andy -- 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
Powered by blists - more mailing lists