From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Julien Tinnes <jln@google.com>,
David Drysdale <drysdale@google.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
LSM List <linux-security-module@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Moore <paul@paul-moore.com>,
James Morris <james.l.morris@oracle.com>,
Linux API <linux-api@vger.kernel.org>,
Meredydd Luff <meredydd@senatehouse.org>,
Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, Theodore Ts'o <tytso@mit.edu>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-crypto@vger.kernel.org
Subject: Re: General flags to turn things off (getrandom, pid lookup, etc)
Date: Wed, 30 Jul 2014 15:37:58 +0100 [thread overview]
Message-ID: <20140730153758.6431fafa@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <CALCETrXHNFYaQjksBJyN3O0HJpKw_D_tU7b4O23=nyJt9CPSLg@mail.gmail.com>
> > We sort of have one. It's called capable(). Just needs extending to cover
> > anything else you care about, and probably all the numeric constants
> > replacing with textual names.
> >
>
> Except that it's all backwards: these are things that default to *on*,
> and people might want them to turn off. capable() is totally fscked
> if you want otherwise unprivileged users to carry capabilities around
The userspace API is, but capable() as a userspace API and capable() as
an in kernel check are only connected by history.
For the in kernel part you can either teach everyone another disjoint API
or we can have a single API in kernel for saying "is XYZ allowed".
next prev parent reply other threads:[~2014-07-30 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:30 General flags to turn things off (getrandom, pid lookup, etc) Andy Lutomirski
2014-07-25 20:15 ` Dave Jones
[not found] ` <20140725201507.GA23410-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-25 20:21 ` Andy Lutomirski
[not found] ` <CALCETrWGvBfrX1W5XaFgJZhKHLf+oac9YrwPR3ppK=deQtu5hA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-25 21:35 ` One Thousand Gnomes
2014-07-25 21:41 ` Andy Lutomirski
2014-07-26 19:48 ` Eric W. Biederman
2014-07-30 14:37 ` One Thousand Gnomes [this message]
2014-07-25 23:43 ` H. Peter Anvin
2014-07-25 23:54 ` Andy Lutomirski
2014-07-27 12:26 ` David Drysdale
2014-07-27 21:06 ` Theodore Ts'o
2014-07-27 22:17 ` Andy Lutomirski
[not found] ` <CALCETrXfzOZEC3mOKkm3_GvitvkEu4kAa3LowRv-fjHnzrQnBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-27 23:53 ` Eric W. Biederman
2014-07-30 14:37 ` One Thousand Gnomes
2014-07-30 18:41 ` Eric W. Biederman
2014-07-30 21:29 ` One Thousand Gnomes
2014-07-31 2:37 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140730153758.6431fafa@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=drysdale@google.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hmh@hmh.eng.br \
--cc=james.l.morris@oracle.com \
--cc=jln@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=meredydd@senatehouse.org \
--cc=paul@paul-moore.com \
--cc=pbonzini@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).