[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1533309815.4337.437.camel@linux.ibm.com>
Date: Fri, 03 Aug 2018 11:23:35 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: David Howells <dhowells@...hat.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
Udit Agarwal <udit.agarwal@....com>, zohar@...ux.vnet.ibm.com,
jmorris@...ei.org, serge@...lyn.com, denkenz@...il.com,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, sahil.malhotra@....com,
ruchika.gupta@....com, horia.geanta@....com, aymen.sghaier@....com
Subject: Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key
support based on CAAM.
On Fri, 2018-08-03 at 15:55 +0100, David Howells wrote:
> Mimi Zohar <zohar@...ux.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
Powered by blists - more mailing lists