Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162337AbbKERem (ORCPT ); Thu, 5 Nov 2015 12:34:42 -0500 Received: from h2.hallyn.com ([78.46.35.8]:58220 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162304AbbKERek (ORCPT ); Thu, 5 Nov 2015 12:34:40 -0500 Date: Thu, 5 Nov 2015 11:34:38 -0600 From: "Serge E. Hallyn" To: Klaus Ethgen Cc: "Serge E. Hallyn" , Andy Lutomirski , Linus Torvalds , Richard Weinberger , LKML , Christoph Lameter , Andy Lutomirski , Serge Hallyn , Kees Cook , Andrew Morton Subject: Re: [KERNEL] Re: [KERNEL] Re: [KERNEL] Re: Kernel 4.3 breaks security in systems using capabilities Message-ID: <20151105173438.GA3378@mail.hallyn.com> References: <20151102191616.GA2158@ikki.ethgen.ch> <20151105101953.GA15293@ikki.ethgen.ch> <20151105161512.GA2180@mail.hallyn.com> <20151105171701.GB9307@ikki.ethgen.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151105171701.GB9307@ikki.ethgen.ch> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1050 Lines: 21 On Thu, Nov 05, 2015 at 06:17:01PM +0100, Klaus Ethgen wrote: > Hi Serge, > > Am Do den 5. Nov 2015 um 17:15 schrieb Serge E. Hallyn: > > I think if you follow your idea to its logical conclusions, you end > > up wanting set SECURE_ALL_BITS | SECURE_ALL_LOCKS, which will include > > SECURE_NO_CAP_AMBIENT_RAISE, disabling ambient capabilities. > > That I did miss out and seems to be the solution for the problem. So > adding cap_secure_all_bits,cap_secure_all_locks=ep to every binary that > gets other caps should solve it? No that doesn't work, you have to use prctl to set those bits. If you can get your system to be fully rootless, you can have init or initramfs do this for you. It'll mean that root and setuid-root binaries have no automatic privileges beside owning host (proc/sys) files. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/