From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
James Morris <jmorris@namei.org>,
keyrings@vger.kernel.org, Netdev <netdev@vger.kernel.org>,
linux-nfs@vger.kernel.org, CIFS <linux-cifs@vger.kernel.org>,
linux-afs@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-integrity@vger.kernel.org,
LSM List <linux-security-module@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Keys: Set 4 - Key ACLs for 5.3
Date: Wed, 21 Aug 2019 19:22:39 +0000 [thread overview]
Message-ID: <19088.1566415359@warthog.procyon.org.uk> (raw)
In-Reply-To: <1566402203.5162.12.camel@linux.ibm.com>
I added a bunch of tests to the keyutils testsuite, currently on my -next
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/log/?h=next
See:
Add a keyctl command for granting a permit on a key
Handle kernel having key/keyring ACLs
I've added manpages to describe the new bits, but I wonder whether I should
add a manpage specifically to detail the permissions system. It'll probably
be useful when more advanced subjects become available, such as for specific
UIDs and for containers-as-a-whole.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
James Morris <jmorris@namei.org>,
keyrings@vger.kernel.org, Netdev <netdev@vger.kernel.org>,
linux-nfs@vger.kernel.org, CIFS <linux-cifs@vger.kernel.org>,
linux-afs@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-integrity@vger.kernel.org,
LSM List <linux-security-module@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Keys: Set 4 - Key ACLs for 5.3
Date: Wed, 21 Aug 2019 20:22:39 +0100 [thread overview]
Message-ID: <19088.1566415359@warthog.procyon.org.uk> (raw)
In-Reply-To: <1566402203.5162.12.camel@linux.ibm.com>
I added a bunch of tests to the keyutils testsuite, currently on my -next
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/log/?h=next
See:
Add a keyctl command for granting a permit on a key
Handle kernel having key/keyring ACLs
I've added manpages to describe the new bits, but I wonder whether I should
add a manpage specifically to detail the permissions system. It'll probably
be useful when more advanced subjects become available, such as for specific
UIDs and for containers-as-a-whole.
David
next prev parent reply other threads:[~2019-08-21 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:30 [GIT PULL] Keys: Set 4 - Key ACLs for 5.3 David Howells
2019-07-05 21:30 ` David Howells
2019-07-09 3:15 ` pr-tracker-bot
2019-07-09 3:15 ` pr-tracker-bot
2019-07-10 18:35 ` Linus Torvalds
2019-07-10 18:35 ` Linus Torvalds
2019-07-10 19:46 ` Eric Biggers
2019-07-10 19:46 ` Eric Biggers
2019-07-10 20:15 ` Eric Biggers
2019-07-10 20:15 ` Eric Biggers
2019-07-11 1:59 ` Linus Torvalds
2019-07-11 1:59 ` Linus Torvalds
2019-07-11 3:07 ` Mimi Zohar
2019-07-11 3:07 ` Mimi Zohar
2019-08-16 13:36 ` David Howells
2019-08-16 13:36 ` David Howells
2019-08-21 14:20 ` Mimi Zohar
2019-08-21 14:20 ` Mimi Zohar
2019-08-21 15:43 ` Mimi Zohar
2019-08-21 15:43 ` Mimi Zohar
2019-08-21 19:22 ` David Howells [this message]
2019-08-21 19:22 ` David Howells
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=19088.1566415359@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.