linux-kernel - Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: Kernel 4.3 breaks security in systems using capabilities

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]

Message-ID: <563CE893.1060309@schaufler-ca.com>
Date:	Fri, 6 Nov 2015 09:51:15 -0800
From:	Casey Schaufler <casey@...aufler-ca.com>
To:	Theodore Ts'o <tytso@....edu>, Klaus Ethgen <Klaus+lkml@...gen.de>,
	"Serge E. Hallyn" <serge@...lyn.com>,
	Andy Lutomirski <luto@...capital.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Richard Weinberger <richard.weinberger@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Lameter <cl@...ux.com>,
	Andy Lutomirski <luto@...nel.org>,
	Serge Hallyn <serge.hallyn@...ntu.com>,
	Kees Cook <keescook@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re:
 Kernel 4.3 breaks security in systems using capabilities

On 11/6/2015 7:53 AM, Theodore Ts'o wrote:
> On Fri, Nov 06, 2015 at 02:58:36PM +0100, Klaus Ethgen wrote:
>> But that left out completely the, I think more important, usecase of
>> _removing_ SUID completely and _replacing_ it with very tight capability
>> setting. And that is what I always talked about.
> I don't believe this is ever going to be possible.  And I'm not
> talking about it from a technical perspective, but from a practical
> and cultural perspective.

There have been rootless systems (e.g. Trusted Irix) in the past.
They sold to a very restricted market and were never widely adopted.
The inevitable first question from the admins was

	"How do I get *real* root?"

I agree that culturally it's a hard sell. Once someone gets a taste
for privilege it's tough to get them to give it up. It's a major
problem even in embedded systems, where people are still doing development
in a root shell.

I was on the POSIX group that defined capabilities. I hate to
say it, but the evidence is that we failed. We've had capabilities
in the kernel for how long? If we haven't been able to make the
transition away from root by now, maybe it's time to reexamine the
way we planned to do it. As I said, we know it's possible. There
are existence proofs. If the product isn't moving, maybe it is time
to put something else on the shelf.

>
> The problem with removing SUID and inheritance completely is that you
> have to anticipate all possible use cases where a system administrator
> might want to use a root shell.  This means analyzing all possible use
> cases for all possible system administrators how they might need to
> use a root shell to fix or management a system, and then either (a)
> provide a new, specialized tool that solves that particular use case,
> while respecting the rules of least privilege, or (b) figure out how
> to expand that executable's fI mask, and worse, if that executable
> fork and exec's helper programs, those helper programs will need to
> have expanded fI masks.  And that's if all of the commands that a
> system administrator needs to run are compiled executables.  Now
> consider what happens when a system administrator needs to run python,
> perl, or shell scripts with elevated privileges.
>
> You maybe can solve this in a very restricted environment; say, one
> really dedicated user who can tweak his or her own's fI masks because
> hopefully he or she can anticipate all possible use cases.  But in the
> general case?  For a general purpose distribution?   Good luck with that.
>
> Schemes like this could work if you are willing to essentially outlaw
> all administrative shell/perl/python scripts.  Otherwise, the fact
> that /bin/sh, /bin/perl, and /bin/python essentially have an unlimited
> fI mask means the whole system has a hole you can drive a truck hole,
> in which case, what's the point of going through the whole effort?
>
> In the light of that, using things like ambient capabilities, or using
> setuid binary that immediately drops all caps that it needs, is
> probably the best we're going to get.
>
> Regards,
>
> 						- Ted
> --
> 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/
>

--
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/