Re: [PATCH v6] pidns: introduce syscall translate_pid

2019-03-08 Thread Nagarathnam Muthusamy
On 11/8/18 7:49 PM, Dmitry V. Levin wrote: Hi, On Mon, Jul 16, 2018 at 10:57:48AM -0700, Nagarathnam Muthusamy wrote: On 06/01/2018 12:18 PM, Konstantin Khlebnikov wrote: Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns tr

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-11-08 Thread Dmitry V. Levin
Hi, On Mon, Jul 16, 2018 at 10:57:48AM -0700, Nagarathnam Muthusamy wrote: > On 06/01/2018 12:18 PM, Konstantin Khlebnikov wrote: > > Each process have different pids, one for each pid namespace it belongs. > > When interaction happens within single pid-ns translation isn't required. > > More comp

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-07-23 Thread Nagarathnam Muthusamy
On 07/23/2018 01:55 PM, Michael Tirado wrote: Hey, I'm not seeing much activity on this so here's my $0.02 Unix socket automatically translates pid attached to SCM_CREDENTIALS. This requires CAP_SYS_ADMIN for sending arbitrary pids and entering into pid namespace, this expose process and cou

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-07-23 Thread Michael Tirado
Hey, I'm not seeing much activity on this so here's my $0.02 > Unix socket automatically translates pid attached to SCM_CREDENTIALS. > This requires CAP_SYS_ADMIN for sending arbitrary pids and entering > into pid namespace, this expose process and could be insecure. Perhaps it would be a good i

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-07-16 Thread Nagarathnam Muthusamy
On 06/01/2018 12:18 PM, Konstantin Khlebnikov wrote: Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns translation isn't required. More complicated scenarios needs special handling. For example: - reading pid-files or logs w

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-07-03 Thread Nagarathnam Muthusamy
On 6/1/2018 12:18 PM, Konstantin Khlebnikov wrote: Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns translation isn't required. More complicated scenarios needs special handling. For example: - reading pid-files or logs wri

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-06-20 Thread Nagarathnam Muthusamy
On 06/01/2018 12:18 PM, Konstantin Khlebnikov wrote: Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns translation isn't required. More complicated scenarios needs special handling. For example: - reading pid-files or logs w

Re: [PATCH v6] pidns: introduce syscall translate_pid

2018-06-12 Thread Nagarathnam Muthusamy
On 06/01/2018 12:18 PM, Konstantin Khlebnikov wrote: Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns translation isn't required. More complicated scenarios needs special handling. For example: - reading pid-files or logs w

[PATCH v6] pidns: introduce syscall translate_pid

2018-06-01 Thread Konstantin Khlebnikov
Each process have different pids, one for each pid namespace it belongs. When interaction happens within single pid-ns translation isn't required. More complicated scenarios needs special handling. For example: - reading pid-files or logs written inside container with pid namespace - writing logs