From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Udit Agarwal <udit.agarwal@nxp.com>,
zohar@linux.vnet.ibm.com, jmorris@namei.org, serge@hallyn.com,
denkenz@gmail.com, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, sahil.malhotra@nxp.com,
ruchika.gupta@nxp.com, horia.geanta@nxp.com,
aymen.sghaier@nxp.com
Subject: Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.
Date: Fri, 03 Aug 2018 15:23:35 +0000 [thread overview]
Message-ID: <1533309815.4337.437.camel@linux.ibm.com> (raw)
In-Reply-To: <25968.1533308142@warthog.procyon.org.uk>
On Fri, 2018-08-03 at 15:55 +0100, David Howells wrote:
> Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> > "trusted" keys are currently being used to decrypt other keys (eg.
> > encrypted, ecryptfs, ...).
>
> Can it decrypt both symmetric and asymmetric keys?
Yes, the "trusted" key is returned to the caller and is used to
decrypt a datablob.
For an example, refer to encrypted_key_decrypt(). The call
to request_master_key() returns either the "trusted" or "user" type
key, which is used to decrypt the "enccrypted" key type.
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Udit Agarwal <udit.agarwal@nxp.com>,
zohar@linux.vnet.ibm.com, jmorris@namei.org, serge@hallyn.com,
denkenz@gmail.com, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, sahil.malhotra@nxp.com,
ruchika.gupta@nxp.com, horia.geanta@nxp.com,
aymen.sghaier@nxp.com
Subject: Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.
Date: Fri, 03 Aug 2018 11:23:35 -0400 [thread overview]
Message-ID: <1533309815.4337.437.camel@linux.ibm.com> (raw)
In-Reply-To: <25968.1533308142@warthog.procyon.org.uk>
On Fri, 2018-08-03 at 15:55 +0100, David Howells wrote:
> Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> > "trusted" keys are currently being used to decrypt other keys (eg.
> > encrypted, ecryptfs, ...).
>
> Can it decrypt both symmetric and asymmetric keys?
Yes, the "trusted" key is returned to the caller and is used to
decrypt a datablob.
For an example, refer to encrypted_key_decrypt(). The call
to request_master_key() returns either the "trusted" or "user" type
key, which is used to decrypt the "enccrypted" key type.
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.
Date: Fri, 03 Aug 2018 11:23:35 -0400 [thread overview]
Message-ID: <1533309815.4337.437.camel@linux.ibm.com> (raw)
In-Reply-To: <25968.1533308142@warthog.procyon.org.uk>
On Fri, 2018-08-03 at 15:55 +0100, David Howells wrote:
> Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> > "trusted" keys are currently being used to decrypt other keys (eg.
> > encrypted, ecryptfs, ...).
>
> Can it decrypt both symmetric and asymmetric keys?
Yes, the "trusted" key is returned to the caller and is used to
decrypt a datablob.
For an example, refer to?encrypted_key_decrypt(). ?The call
to?request_master_key() returns either the "trusted" or "user" type
key, which is used to decrypt the "enccrypted" key type.
Mimi
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Udit Agarwal <udit.agarwal@nxp.com>,
zohar@linux.vnet.ibm.com, jmorris@namei.org, serge@hallyn.com,
denkenz@gmail.com, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, sahil.malhotra@nxp.com,
ruchika.gupta@nxp.com, horia.geanta@nxp.com,
aymen.sghaier@nxp.com
Subject: Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.
Date: Fri, 03 Aug 2018 11:23:35 -0400 [thread overview]
Message-ID: <1533309815.4337.437.camel@linux.ibm.com> (raw)
In-Reply-To: <25968.1533308142@warthog.procyon.org.uk>
On Fri, 2018-08-03 at 15:55 +0100, David Howells wrote:
> Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> > "trusted" keys are currently being used to decrypt other keys (eg.
> > encrypted, ecryptfs, ...).
>
> Can it decrypt both symmetric and asymmetric keys?
Yes, the "trusted" key is returned to the caller and is used to
decrypt a datablob.
For an example, refer to encrypted_key_decrypt(). The call
to request_master_key() returns either the "trusted" or "user" type
key, which is used to decrypt the "enccrypted" key type.
Mimi
next prev parent reply other threads:[~2018-08-03 15:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 11:14 [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM Udit Agarwal
2018-07-23 11:26 ` Udit Agarwal
2018-07-23 11:14 ` Udit Agarwal
2018-07-23 11:14 ` [PATCH v2 2/2] encrypted_keys: Adds support for secure key-type as master key Udit Agarwal
2018-07-23 11:26 ` Udit Agarwal
2018-07-23 11:14 ` Udit Agarwal
2018-08-02 16:14 ` [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM David Howells
2018-08-02 16:14 ` David Howells
2018-08-02 16:14 ` David Howells
2018-08-02 18:57 ` James Bottomley
2018-08-02 18:57 ` James Bottomley
2018-08-02 18:57 ` James Bottomley
2018-08-03 11:58 ` Mimi Zohar
2018-08-03 11:58 ` Mimi Zohar
2018-08-03 11:58 ` Mimi Zohar
2018-08-03 11:58 ` Mimi Zohar
2018-08-03 14:23 ` James Bottomley
2018-08-03 14:23 ` James Bottomley
2018-08-03 14:23 ` James Bottomley
2018-08-03 14:23 ` James Bottomley
2018-08-03 14:45 ` Mimi Zohar
2018-08-03 14:45 ` Mimi Zohar
2018-08-03 14:45 ` Mimi Zohar
2018-08-03 14:45 ` Mimi Zohar
2018-08-03 15:48 ` James Bottomley
2018-08-03 15:48 ` James Bottomley
2018-08-03 15:48 ` James Bottomley
2018-08-03 15:48 ` James Bottomley
2018-08-03 18:28 ` Mimi Zohar
2018-08-03 18:28 ` Mimi Zohar
2018-08-03 18:28 ` Mimi Zohar
2018-08-03 18:28 ` Mimi Zohar
2018-10-16 10:16 ` David Gstir
2018-10-16 10:16 ` David Gstir
2018-10-16 10:16 ` David Gstir
2018-08-03 14:55 ` David Howells
2018-08-03 14:55 ` David Howells
2018-08-03 14:55 ` David Howells
2018-08-03 15:23 ` Mimi Zohar [this message]
2018-08-03 15:23 ` Mimi Zohar
2018-08-03 15:23 ` Mimi Zohar
2018-08-03 15:23 ` Mimi Zohar
2020-01-17 11:52 ` Maik Otto
2020-01-17 11:52 ` Maik Otto
2020-01-23 12:55 ` Jarkko Sakkinen
2020-01-23 12:55 ` 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=1533309815.4337.437.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aymen.sghaier@nxp.com \
--cc=denkenz@gmail.com \
--cc=dhowells@redhat.com \
--cc=horia.geanta@nxp.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ruchika.gupta@nxp.com \
--cc=sahil.malhotra@nxp.com \
--cc=serge@hallyn.com \
--cc=udit.agarwal@nxp.com \
--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 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.