From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH v2 2/3] key: Make key/keychain revocation optional when freeing
Date: Mon, 24 Oct 2016 20:59:41 -0500 [thread overview]
Message-ID: <580EBC8D.3060305@gmail.com> (raw)
In-Reply-To: <20161024213633.10668-2-mathew.j.martineau@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Hi Mat,
On 10/24/2016 04:36 PM, Mat Martineau wrote:
> Revoking keys (or keyrings) unlinks them from every keyring. Sometimes
> it is useful to let the kernel keep a key even if ELL isn't directly
> tracking that key anymore - for example, a keyring of trusted keys can
> be used for validation without keeping l_key objects around for every
> single key in that keyring. The kernel will clean up the kernel key
> objects when there are no more references to them whether or not we
> explicitly revoke from userspace.
>
> l_key_free_norevoke and l_keyring_free_norevoke are added to support the
> non-revoking behavior, while the default is still to revoke the key.
> ---
> ell/key.c | 20 ++++++++++++++++++++
> ell/key.h | 2 ++
> 2 files changed, 22 insertions(+)
>
Applied, thanks.
Regards,
-Denis
next prev parent reply other threads:[~2016-10-25 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 21:36 [PATCH v2 1/3] unit: Fix memory leak in trust chain test Mat Martineau
2016-10-24 21:36 ` [PATCH v2 2/3] key: Make key/keychain revocation optional when freeing Mat Martineau
2016-10-25 1:59 ` Denis Kenzior [this message]
2016-10-24 21:36 ` [PATCH v2 3/3] tls: Validate cert chain using l_keyring Mat Martineau
2016-10-25 2:19 ` Denis Kenzior
2016-10-25 1:59 ` [PATCH v2 1/3] unit: Fix memory leak in trust chain test Denis Kenzior
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=580EBC8D.3060305@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.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.