netdev - Re: Question about netns & AF

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

Message-ID: <AANLkTim208jFNjlPelRnt849s3isVlyrtSXcLrUzIsZX@mail.gmail.com>
Date:	Mon, 31 May 2010 11:19:52 +0200
From:	Martín Ferrari <martin.ferrari@...il.com>
To:	Dan Smith <danms@...ibm.com>
Cc:	netdev <netdev@...r.kernel.org>,
	Mathieu Lacage <mathieu.lacage@...hia.inria.fr>
Subject: Re: Question about netns & AF_UNIX

Hi,

On Thu, May 27, 2010 at 20:08, Dan Smith <danms@...ibm.com> wrote:

> If you are in different network namespaces, the binding of UNIX
> sockets is also kept separate.  Even though the filesystem is shared,
> this seems to make the most sense to me.

To me it was the opposite, I thought natural that UNIX sockets would
continue to work, at least when they are bound to a filesystem entry.
Also it is a nice and clean way to communicate across namespaces
without assuming lots of things about the network configuration.

> Named pipes on the
> filesystem would still be shared, by the way.

Yes, today I've tried with named pipes and worked. It's just that they
aren't as nice as UNIX sockets :)

Thanks.

-- 
Martín Ferrari
--
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