All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <jejb@linux.vnet.ibm.com>
To: keyrings@vger.kernel.org
Subject: Re: [RFCv3 08/13] KEYS: asym_tpm: Add loadkey2 and flushspecific
Date: Wed, 08 Aug 2018 15:53:37 +0000	[thread overview]
Message-ID: <1533743617.4044.13.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180802183121.22909-9-denkenz@gmail.com>

On Wed, 2018-08-08 at 10:49 -0500, Denis Kenzior wrote:
> Hi David,
> 
> On 08/08/2018 10:46 AM, David Howells wrote:
> > Denis Kenzior <denkenz@gmail.com> wrote:
> > 
> > > +#include "../../security/keys/trusted.h"
> > 
> > Should this be moved to include/keys/ somewhere, at least in part?
> > 
> 
> That is one of the questions in my mind as well.  Should we factor
> out the core TPM primitives out of trusted.[ch] into a separate
> library / module or just have asym_tpm depend on the trusted
> subtype.  I have no real preference here as long as the stuff in
> trusted.[ch] can be shared somehow.
> 
> If you want to simply move trusted.h to include/keys that would be
> good with me as well.

I'm happy with that.  The trusted code is a bit of a mess at the
moment: all the tpm1.2 handling is inside trusted.c but the tpm2
handling is done by callouts to drivers/char/tpm/

I think, ideally, the tpm1.2 pieces should similarly move into
drivers/char/tpm/

James


      parent reply	other threads:[~2018-08-08 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 18:31 [RFCv3 08/13] KEYS: asym_tpm: Add loadkey2 and flushspecific Denis Kenzior
2018-08-07 20:07 ` James Morris
2018-08-08 15:46 ` David Howells
2018-08-08 15:49 ` Denis Kenzior
2018-08-08 15:53 ` James Bottomley [this message]

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=1533743617.4044.13.camel@linux.vnet.ibm.com \
    --to=jejb@linux.vnet.ibm.com \
    --cc=keyrings@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.