From: Mimi Zohar <zohar@linux.ibm.com>
To: Yael Tzur <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@vger.kernel.org
Subject: Re: [PATCH v5] KEYS: encrypted: Instantiate key with user-provided decrypted data
Date: Mon, 21 Feb 2022 00:11:22 -0500 [thread overview]
Message-ID: <0aa47dfaada88f1cbd2162784f8b77f43566f626.camel@linux.ibm.com> (raw)
In-Reply-To: <20220215141953.1557009-1-yaelt@google.com>
On Tue, 2022-02-15 at 09:19 -0500, Yael Tzur wrote:
> For availability and performance reasons master keys often need to be
> released outside of a Key Management Service (KMS) to clients. It
> would be beneficial to provide a mechanism where the
> wrapping/unwrapping of data encryption keys (DEKs) is not dependent
> on a remote call at runtime yet security is not (or only minimally)
> compromised. Master keys could be securely stored in the Kernel and
> be used to wrap/unwrap keys from Userspace.
>
> 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. This patch defines a new datablob
> format: [<format>] <master-key name> <decrypted data length>
> <decrypted data> that allows to inject and encrypt user-provided
> decrypted data. The decrypted data must be hex-ascii encoded.
>
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> Signed-off-by: Yael Tzur <yaelt@google.com>
Thanks, Yael.
This patch is now queued in the #next-integrity-testing branch.
--
thanks,
Mimi
next prev parent reply other threads:[~2022-02-21 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 14:19 [PATCH v5] KEYS: encrypted: Instantiate key with user-provided decrypted data Yael Tzur
2022-02-21 5:11 ` Mimi Zohar [this message]
2022-02-21 20:19 ` Jarkko Sakkinen
2022-02-21 5:47 ` Sumit Garg
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=0aa47dfaada88f1cbd2162784f8b77f43566f626.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;
as well as URLs for NNTP newsgroup(s).