netdev - Re: netlink versus pid namespaces

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:	Fri, 15 Oct 2010 19:19:03 +0400
From:	Alexey Kuznetsov <kuznet@....inr.ac.ru>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	netdev@...r.kernel.org, xemul@...nvz.org,
	virtualization@...ts.linux-foundation.org
Subject: Re: netlink versus pid namespaces

Hello!

> netlink uses pids (or really tids I hope?) to address sockets
> associated with processes.

Not really. It uses port number which is called "pid" occasionally. Bad name.
Autobind function simply selects tgid of calling process as the first guess.

Actually sockets are addressed by pair (net namespace, port) and
communication is possible only inside net namespace. So, communication
between namespaces is already prohibited.

pid namespaces do not participate in the picture at all.

Alexey
--
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