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  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:	Mon, 08 Mar 2010 14:24:30 -0800
From: (Eric W. Biederman)
To:	"Serge E. Hallyn" <>
Cc:	Daniel Lezcano <>,
	Pavel Emelyanov <>,
	Sukadev Bhattiprolu <>,
	Linux Netdev List <>,,
	Netfilter Development Mailinglist 
	Ben Greear <>
Subject: Re: [RFC][PATCH] ns: Syscalls for better namespace sharing control.

"Serge E. Hallyn" <> writes:

> Quoting Eric W. Biederman (
>> Daniel Lezcano <> writes:
>> I guess my meaning is I was expecting.
>> child = fork();
>> if (child == 0) {
>> 	execve(...);
>> }
>> waitpid(child);
>> This puts /bin/sh in the container as well.
>> I'm not certain about the /proc/self thing I have never encountered that.
>> But I guess if your pid is outside of the pid namespace of that instance
>> of proc /proc/self will be a broken symlink.
>> Eric
> Hmm, worse than a broken symlink, will it be a wrong symlink if just
> the right pid is created in the container?

It won't happen. readlink and followlink are both based on 
task_tgid_nr_ns(current, ns_of_proc).

Which fails if your process is not known in that pid namespace.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists