netdev - Re: AF_UNIX sockets crossing namespace based boundaries

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]

Date:   Wed, 2 Jan 2019 15:05:14 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Donald Sharp <sharpd@...ulusnetworks.com>
Cc:     netdev@...r.kernel.org, David Ahern <dsa@...ulusnetworks.com>,
        Nicolas Dichtel <nicolas.dichtel@...nd.com>,
        Roopa Prabhu <roopa@...ulusnetworks.com>
Subject: Re: AF_UNIX sockets crossing namespace based boundaries

On Tue, Jan 01, 2019 at 07:46:07PM -0500, Donald Sharp wrote:
> I have created multiple namespaces:
> 
> sharpd@...ot /v/l/frr> ip netns list
> two (id: 2)
> one (id: 1)
> EVA (id: 0)
> 
> And am running a process in namespace two that creates a named socket
> `/var/log/frr/run/zserv.api`:

Hi Donald

Just to be sure...

Are you creating only a network name space, and not a filesystem mount
namespace?

I've successfully run hundred of FRR daemons in namespaces on Linux
for simulation work, but i always use both a network namespace and
mount namespace. /var/log/frr/run/zserv.api is clearly a filesystem
path, so you need to separate these at the filesystem level.

       Andrew