From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
linux-nfs@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] [RFC] KEYS: Add invalidation support
Date: Thu, 15 Dec 2011 13:14:23 +0000 [thread overview]
Message-ID: <5110.1323954863@redhat.com> (raw)
In-Reply-To: <1323953422.15982.13.camel@falcor>
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> Not all keys can be 'refetched'. A trusted key, sealed to a PCR, can
> extend the PCR to prevent it from being re-loaded. Removing the trusted
> key could prevent the instantiation/update of encrypted keys.
I meant discard and set up a new struct key not actually invalidate any real
key store. Is this actually a problem? If it is, I can certainly add a flag
to prevent struct keys from being invalidated; but that doesn't stop them from
being unlinked or revoked.
David
next prev parent reply other threads:[~2011-12-15 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 12:17 [PATCH] [RFC] KEYS: Add invalidation support David Howells
2011-12-15 12:50 ` Mimi Zohar
2011-12-15 13:14 ` David Howells [this message]
2011-12-15 21:30 ` Mimi Zohar
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=5110.1323954863@redhat.com \
--to=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox