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

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

Message-ID: <4BFED31C.2070702@free.fr>
Date:	Thu, 27 May 2010 22:16:28 +0200
From:	Daniel Lezcano <daniel.lezcano@...e.fr>
To:	Martín Ferrari <martin.ferrari@...il.com>
CC:	netdev <netdev@...r.kernel.org>,
	Mathieu Lacage <mathieu.lacage@...hia.inria.fr>
Subject: Re: Question about netns & AF_UNIX

On 05/27/2010 04:38 PM, Martín Ferrari wrote:
> Hi, again a question about netns...
>
> I seem to recall being able to use AF_UNIX sockets across network name
> spaces, but I cannot reproduce that with a current kernel. Probably my
> test was fubar (I've lost the script).
>    

No, that was never the case. Maybe you tested with a patched kernel 
allowing to cross-namespace connect.
> In any case: is a design decision to forbid this, even when the file
> system is shared? I found some discussions from 2008, but I don't see
> an agreement being reached...
>    

There was a discussion about that but with a simple hack removing the 
test against the namespace when connecting.
The problem is nobody investigated that against credentials in ancillary 
messages, or other particularity of the af_unix socket vs the namespaces.

> I also wonder if filedescriptor passing thru ancilliary messages will
> work (that is, with unix sockets that I've created before the netns
> change).
>    

Yes.

Thanks
   -- Daniel
--
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