linux-kernel - Re: [RFC c/r 3/4] c/r: procfs: add arg_start/end, env_start/end and exit

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:	Sat, 28 Jan 2012 00:10:22 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	ebiederm@...ssion.com, xemul@...nvz.org, xemul@...allels.com,
	serge.hallyn@...onical.com, keescook@...omium.org,
	kamezawa.hiroyu@...fujitsu.com, adobriyan@...il.com, tj@...nel.org,
	avagin@...nvz.org, segoon@...nwall.com
Subject: Re: [RFC c/r 3/4] c/r: procfs: add arg_start/end, env_start/end and
 exit_code members to /proc/$pid/stat

On Fri, Jan 27, 2012 at 03:00:37PM -0500, KOSAKI Motohiro wrote:
...
> 
> > +
> > +		seq_printf(m, "%d\n", task->exit_code);
> > +
> 
> Bad this part seems to make new side channel. exit_code is one of
> inter process communication messages. IPC messages should NOT be
> observed from completely unrelated proesses.
> 

You mean we need "permitted" test here, right?

	Cyrill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/