From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
dmitry.kasatkin@gmail.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, David Safford <safford@us.ibm.com>
Subject: Re: RFC: 'ioctl' for keyrings
Date: Fri, 14 Mar 2014 17:14:35 +0000 [thread overview]
Message-ID: <7511.1394817275@warthog.procyon.org.uk> (raw)
In-Reply-To: <1394729834.8457.58.camel@dhcp-9-2-203-236.watson.ibm.com>
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> > As I understand the code, I think operations being performed from ->update()
> > are:
> >
> > (a) Resealing a key with a new pcrs (trusted).
> >
> > (b) Changing the master key (encrypted).
> >
> > Mimi, Dmitry: is this list right?
>
> In addition to resealing trusted keys to a new TPM PCR value, there are
> a few other options that can be modified (eg. keyauth, blobauth,
> pcrlock). Encrypted keys can be encrypted/decrypted with a new master
> key (trusted or user key type).
Can (re)sealing a key be viewed as encrypting it? Is the difference between
sealing a key and encrypting a key the use of hardware support?
David
next prev parent reply other threads:[~2014-03-14 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:47 David Howells
2014-03-13 16:17 ` David Howells
2014-03-13 16:40 ` Mimi Zohar
2014-03-13 16:57 ` Mimi Zohar
2014-03-14 17:14 ` David Howells [this message]
2014-03-14 17:53 ` 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=7511.1394817275@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®