From: mathew.j.martineau@linux.intel.com (Mat Martineau)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v13 00/10] Make keyring link restrictions accessible from userspace
Date: Mon, 3 Apr 2017 13:25:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.OSX.2.21.1704031317130.6711@mjmartin-mac01.local> (raw)
In-Reply-To: <3861.1491235163@warthog.procyon.org.uk>
On Mon, 3 Apr 2017, David Howells wrote:
> David Howells <dhowells@redhat.com> wrote:
>
>> I've just updated my keys-blacklist and keys-next branches to security/next.
>> Could you rebase on that so that I can pull it? There shouldn't be any need
>> to repost your patches unless you need to make changes.
>
> Rebasing on security/next would also do if your patches don't depend on my
> blacklist patches.
Thanks, David. The rebase did not have any conflicts, so I have not made
changes to the posted patches.
You can pull from the keyctl-restrict branch of
https://git.kernel.org/pub/scm/linux/kernel/git/martineau/linux.git
(commit id c06c4d85cc986688c8f7e510412485ab4422a334)
--
Mat Martineau
Intel OTC
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-03 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 23:50 [PATCH v13 00/10] Make keyring link restrictions accessible from userspace Mat Martineau
2017-03-30 23:50 ` [PATCH v13 01/10] KEYS: Use a typedef for restrict_link function pointers Mat Martineau
2017-03-30 23:50 ` [PATCH v13 02/10] KEYS: Split role of the keyring pointer for keyring restrict functions Mat Martineau
2017-03-30 23:50 ` [PATCH v13 03/10] KEYS: Add a key restriction struct Mat Martineau
2017-03-30 23:50 ` [PATCH v13 04/10] KEYS: Use structure to capture key restriction function and data Mat Martineau
2017-03-30 23:50 ` [PATCH v13 05/10] KEYS: Add an optional lookup_restriction hook to key_type Mat Martineau
2017-03-30 23:50 ` [PATCH v13 06/10] KEYS: Consistent ordering for __key_link_begin and restrict check Mat Martineau
2017-03-30 23:50 ` [PATCH v13 07/10] KEYS: Add KEYCTL_RESTRICT_KEYRING Mat Martineau
2017-03-30 23:50 ` [PATCH v13 08/10] KEYS: Add a lookup_restriction function for the asymmetric key type Mat Martineau
2017-03-30 23:50 ` [PATCH v13 09/10] KEYS: Restrict asymmetric key linkage using a specific keychain Mat Martineau
2017-03-30 23:50 ` [PATCH v13 10/10] KEYS: Keyring asymmetric key restrict method with chaining Mat Martineau
2017-04-03 15:24 ` [PATCH v13 00/10] Make keyring link restrictions accessible from userspace David Howells
2017-04-03 15:59 ` David Howells
2017-04-03 20:25 ` Mat Martineau [this message]
2017-04-03 23:02 ` David Howells
2017-04-04 7:28 ` David Howells
2017-04-04 7:30 ` 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=alpine.OSX.2.21.1704031317130.6711@mjmartin-mac01.local \
--to=mathew.j.martineau@linux.intel.com \
--cc=linux-security-module@vger.kernel.org \
/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).