From: Eric Biggers <ebiggers@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: James Morris <jmorris@namei.org>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] keys: Miscellany
Date: Wed, 29 May 2019 22:11:53 +0000 [thread overview]
Message-ID: <20190529221152.GD141639@gmail.com> (raw)
In-Reply-To: <18289.1559167295@warthog.procyon.org.uk>
On Wed, May 29, 2019 at 11:01:35PM +0100, David Howells wrote:
>
> (2) Implement a keyctl to allow a key to be moved from one keyring to
> another, with the option of prohibiting key replacement in the
> destination keyring.
>
What is the use case, and where are the tests and documentation for this?
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: James Morris <jmorris@namei.org>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] keys: Miscellany
Date: Wed, 29 May 2019 15:11:53 -0700 [thread overview]
Message-ID: <20190529221152.GD141639@gmail.com> (raw)
In-Reply-To: <18289.1559167295@warthog.procyon.org.uk>
On Wed, May 29, 2019 at 11:01:35PM +0100, David Howells wrote:
>
> (2) Implement a keyctl to allow a key to be moved from one keyring to
> another, with the option of prohibiting key replacement in the
> destination keyring.
>
What is the use case, and where are the tests and documentation for this?
- Eric
next prev parent reply other threads:[~2019-05-29 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 22:01 [GIT PULL] keys: Miscellany David Howells
2019-05-29 22:01 ` David Howells
2019-05-29 22:11 ` Eric Biggers [this message]
2019-05-29 22:11 ` Eric Biggers
2019-05-30 6:53 ` James Morris
2019-05-30 6:53 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2016-07-08 18:15 [GIT PULL] KEYS: Miscellany 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=20190529221152.GD141639@gmail.com \
--to=ebiggers@kernel.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.