From: Mimi Zohar <zohar@linux.ibm.com>
To: Yael Tiomkin <yaelt@google.com>, linux-integrity@vger.kernel.org
Cc: jejb@linux.ibm.com, jarkko@kernel.org, corbet@lwn.net,
dhowells@redhat.com, jmorris@namei.org, serge@hallyn.com,
keyrings@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v2] Instantiate key with user-provided decrypted data.
Date: Tue, 14 Dec 2021 07:37:30 -0500 [thread overview]
Message-ID: <ec2ec0a9a7ba1adc6e54bbf7051a83ba90a39c0b.camel@linux.ibm.com> (raw)
In-Reply-To: <20211213192030.125091-1-yaelt@google.com>
Hi Yael,
On Mon, 2021-12-13 at 14:20 -0500, Yael Tiomkin wrote:
> The encrypted.c class supports instantiation of encrypted keys with
> either an already-encrypted key material, or by generating new key
> material based on random numbers. To support encryption of
> user-provided decrypted data, this patch defines a new datablob
> format: [<format>] <master-key name> <decrypted data length>
> <decrypted data>.
>
> Signed-off-by: Yael Tiomkin <yaelt@google.com>
Other than the comment below,
Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
Could you also provide an LTP test for defining, exporting, and loading
an encrypted key based on user provided key data?
thanks,
Mimi
> ---
> @@ -303,6 +306,16 @@ Load an encrypted key "evm" from saved blob::
> 82dbbc55be2a44616e4959430436dc4f2a7a9659aa60bb4652aeb2120f149ed197c564e0
> 24717c64 5972dcb82ab2dde83376d82b2e3c09ffc
>
> +Instantiate an encrypted key "evm" using user-provided decrypted data::
> +
> + $ keyctl add encrypted evm "new default user:kmk 32 `cat evm.blob`" @u
> + 794890253
The existing references to "evm.blob" refer to the encrypted key data.
Here "evm.blob" is unencrypted data. Perhaps name it something like
"evm.user-provided-data" data.
> +
> + $ keyctl print 794890253
> + default user:kmk 32 2375725ad57798846a9bbd240de8906f006e66c03af53b1b382d
> + bbc55be2a44616e4959430436dc4f2a7a9659aa60bb4652aeb2120f149ed197c564e0247
> + 17c64 5972dcb82ab2dde83376d82b2e3c09ffc
> +
next prev parent reply other threads:[~2021-12-14 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 19:20 Yael Tiomkin
2021-12-14 12:37 ` Mimi Zohar [this message]
2021-12-22 16:31 ` Yael Tiomkin
2021-12-22 17:42 ` Mimi Zohar
2021-12-21 8:28 ` Jarkko Sakkinen
2021-12-21 8:30 ` Jarkko Sakkinen
2021-12-21 12:05 ` 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=ec2ec0a9a7ba1adc6e54bbf7051a83ba90a39c0b.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=yaelt@google.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®