linux-kernel - Re: [patch] file capabilities: Add no_file

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:	Wed, 27 Aug 2008 17:32:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Howells <dhowells@...hat.com>
Cc:	"Serge E. Hallyn" <serue@...ibm.com>, dhowells@...hat.com,
	Andreas Gruenbacher <agruen@...e.de>,
	"Andrew G. Morgan" <morgan@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] file capabilities: Add no_file_caps switch

On Wed, 27 Aug 2008 17:13:24 +0100
David Howells <dhowells@...hat.com> wrote:

> Serge E. Hallyn <serue@...ibm.com> wrote:
> 
> > (Also note that if you have such users, you'll want to ask David Howells not
> > to push the patch he has floated removing the ability to pass caps to
> > another task altogether when CONFIG_SECURITY_FILE_CAPABILITIES=n :)
> 
> Ugh.  My patch removes the ability to pass caps to another task under all
> circumstances because to do otherwise means that I have to make the kernel use
> RCU locking for a task to access its own creds.  If you want this, I'll have
> to redo all my later patches.

That gets foul in another way - bounding the worst case RCU
memory utilisation if someone is sitting doing things like while(1)
change_credentials();
--
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/