All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
	David Woodhouse <dwmw2@infradead.org>,
	keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v9 0/8] TPM 2.0 trusted keys with attached policy
Date: Sat, 16 May 2020 12:33:22 +0000	[thread overview]
Message-ID: <4d2ff03c7869b5f5ba5c84da6720078628040980.camel@linux.intel.com> (raw)
In-Reply-To: <20200515191758.ieojyk5xhsx2hzzd@cantor>

On Fri, 2020-05-15 at 12:17 -0700, Jerry Snitselaar wrote:
> > > > sudo ./keyctl-smoke.sh
> > > > 566201053 (0x80000000)
> > > > keyctl_read_alloc: Permission denied
> 
> I get keyctl_read_alloc -EPERM when I 'sudo su' and try to play with keyctl print.
> If I 'sudo su -' and then try it works as expected. Also works for normal user.

Can confirm these results with NUC7PJYH (Gemini Lake).

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
	David Woodhouse <dwmw2@infradead.org>,
	keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v9 0/8] TPM 2.0 trusted keys with attached policy
Date: Sat, 16 May 2020 15:33:22 +0300	[thread overview]
Message-ID: <4d2ff03c7869b5f5ba5c84da6720078628040980.camel@linux.intel.com> (raw)
In-Reply-To: <20200515191758.ieojyk5xhsx2hzzd@cantor>

On Fri, 2020-05-15 at 12:17 -0700, Jerry Snitselaar wrote:
> > > > sudo ./keyctl-smoke.sh
> > > > 566201053 (0x80000000)
> > > > keyctl_read_alloc: Permission denied
> 
> I get keyctl_read_alloc -EPERM when I 'sudo su' and try to play with keyctl print.
> If I 'sudo su -' and then try it works as expected. Also works for normal user.

Can confirm these results with NUC7PJYH (Gemini Lake).

/Jarkko


  parent reply	other threads:[~2020-05-16 12:33 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 23:11 [PATCH v9 0/8] TPM 2.0 trusted keys with attached policy James Bottomley
2020-05-07 23:11 ` James Bottomley
2020-05-07 23:11 ` [PATCH v9 1/8] lib: add ASN.1 encoder James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-17  8:17   ` Sakkinen, Jarkko
2020-05-17  8:17     ` Sakkinen, Jarkko
2020-05-07 23:11 ` [PATCH v9 2/8] oid_registry: Add TCG defined OIDS for TPM keys James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-07 23:11 ` [PATCH v9 3/8] security: keys: trusted: fix TPM2 authorizations James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-14  1:11   ` Jarkko Sakkinen
2020-05-14  1:11     ` Jarkko Sakkinen
2020-05-14  1:12     ` Jarkko Sakkinen
2020-05-14  1:12       ` Jarkko Sakkinen
2020-05-14  1:41       ` James Bottomley
2020-05-14  1:41         ` James Bottomley
2020-05-14 11:19         ` Jarkko Sakkinen
2020-05-14 11:19           ` Jarkko Sakkinen
2020-05-07 23:11 ` [PATCH v9 4/8] security: keys: trusted: use ASN.1 TPM2 key format for the blobs James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-17  8:18   ` Sakkinen, Jarkko
2020-05-17  8:18     ` Sakkinen, Jarkko
2020-05-07 23:11 ` [PATCH v9 5/8] security: keys: trusted: Make sealed key properly interoperable James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-07 23:11 ` [PATCH v9 6/8] security: keys: trusted: add PCR policy to TPM2 keys James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-07 23:11 ` [PATCH v9 7/8] security: keys: trusted: add ability to specify arbitrary policy James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-07 23:11 ` [PATCH v9 8/8] security: keys: trusted: implement counter/timer policy James Bottomley
2020-05-07 23:11   ` James Bottomley
2020-05-14 14:31 ` [PATCH v9 0/8] TPM 2.0 trusted keys with attached policy Jarkko Sakkinen
2020-05-14 14:31   ` Jarkko Sakkinen
2020-05-15  2:22   ` Jarkko Sakkinen
2020-05-15  2:22     ` Jarkko Sakkinen
2020-05-15  3:44     ` James Bottomley
2020-05-15  3:44       ` James Bottomley
2020-05-15  8:47       ` Jarkko Sakkinen
2020-05-15  8:47         ` Jarkko Sakkinen
2020-05-15  9:30         ` Jerry Snitselaar
2020-05-15  9:30           ` Jerry Snitselaar
2020-05-15 18:48           ` James Bottomley
2020-05-15 18:48             ` James Bottomley
2020-05-16 12:24             ` Jarkko Sakkinen
2020-05-16 12:24               ` Jarkko Sakkinen
2020-05-16  9:59           ` Jarkko Sakkinen
2020-05-16  9:59             ` Jarkko Sakkinen
2020-05-15 19:17         ` Jerry Snitselaar
2020-05-15 19:17           ` Jerry Snitselaar
2020-05-15 19:34           ` James Bottomley
2020-05-15 19:34             ` James Bottomley
2020-05-15 19:50             ` Mimi Zohar
2020-05-15 19:50               ` Mimi Zohar
2020-05-15 20:10             ` James Bottomley
2020-05-15 20:10               ` James Bottomley
2020-05-15 21:03               ` Kayaalp, Mehmet
2020-05-15 22:19                 ` James Bottomley
2020-05-15 22:19                   ` James Bottomley
2020-05-15 23:23                   ` James Bottomley
2020-05-15 23:23                     ` James Bottomley
2020-05-16 21:44                     ` Jarkko Sakkinen
2020-05-16 21:44                       ` Jarkko Sakkinen
2020-05-16 13:01               ` Sakkinen, Jarkko
2020-05-16 13:01                 ` Sakkinen, Jarkko
2020-05-16 12:33           ` Jarkko Sakkinen [this message]
2020-05-16 12:33             ` Jarkko Sakkinen

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=4d2ff03c7869b5f5ba5c84da6720078628040980.camel@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jsnitsel@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.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 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.