[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFLxGvxO7EtBapTuO5vWuS20hdRxPxr=s=Co7=kTbh8DhFWEuA@mail.gmail.com>
Date: Sat, 11 Jul 2015 13:30:52 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: Casey Schaufler <casey@...aufler-ca.com>
Cc: David Herrmann <dh.herrmann@...il.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Greg KH <gregkh@...uxfoundation.org>,
Daniel Mack <daniel@...que.org>,
Djalal Harouni <tixxdz@...ndz.org>,
lkml <linux-kernel@...r.kernel.org>,
LSM <linux-security-module@...r.kernel.org>,
Paul Osmialowski <p.osmialowsk@...sung.com>,
Paul Moore <paul@...l-moore.com>
Subject: Re: kdbus: credential faking
On Fri, Jul 10, 2015 at 8:36 PM, Casey Schaufler <casey@...aufler-ca.com> wrote:
> On some systems the uid is being used as an application identifier
> instead of a human identifier. The access controls are not designed
> for this. The POSIX capabilities aren't designed for this. If Fred
> creates a program that is setuid to fred and gets Barney to run it,
> you hold Fred accountable. If a malicious (or compromised) application
> identified by "fred" creates a setuid fred program and the "barney"
> application runs it, who do you hold accountable? It's a completely
> different mindset. Sure, you can wedge the one into the other, but
> it's not the intended use. Hence, misuse or abuse.
Actually that's an interesting thought.
The question is whether the /run/user/<uid>/bus security model works
also for "special" userland like Android.
To my knowledge on Android each application runs as different user.
If kdbus gets merged it would be nice to have to work with all kinds of userland
and not only Fedora.
--
Thanks,
//richard
--
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