[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130914111426.GB4663@cachalot>
Date: Sat, 14 Sep 2013 15:14:26 +0400
From: Vasiliy Kulikov <segoon@...nwall.com>
To: Christian Kujau <lists@...dbynature.de>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: proc hidepid=2 and SGID programs
On Tue, Sep 10, 2013 at 01:30 -0700, Christian Kujau wrote:
> On Sun, 8 Sep 2013 at 23:42, Eric W. Biederman wrote:
> > I don't have a clue why anyone would want to hide processes, and make
> > their own lives more difficult.
>
> Oh, there are plenty of usescases, I'm sure. And I for one am thankful
> that this process hiding option made it into the kernel. Or, to answer in
> another way: why would anyone want to see other peoples processes?
The point is that quite many information about other user processes
which can be obtained from procfs can be used in side channel attacks
directed to either confidentiality or even privilege escalation.
> > The check with hidepid is can you ptrace the process. I expect there
> > is something with those sgid processes that keeps you from ptracing
> > them.
>
> Indeed, I cannot strace the process.
Right.
> But still, I wonder if this is
> intended behaviour.
Yes.
If you think such side channel attacks are something you don't care,
just turn hidepid off. That's why it is an option.
If you want to turn it off for some users, use gid=XXX.
--
Vasily Kulikov
http://www.openwall.com - bringing security into open computing environments
--
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/
Powered by blists - more mailing lists