linux-kernel - Re: [PATCH v5] KEYS: encrypted: Instantiate key with user-provided decrypted data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0aa47dfaada88f1cbd2162784f8b77f43566f626.camel@linux.ibm.com>
Date:   Mon, 21 Feb 2022 00:11:22 -0500
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Yael Tzur <yaelt@...gle.com>, linux-integrity@...r.kernel.org
Cc:     jejb@...ux.ibm.com, jarkko@...nel.org, corbet@....net,
        dhowells@...hat.com, jmorris@...ei.org, serge@...lyn.com,
        keyrings@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH v5] KEYS: encrypted: Instantiate key with user-provided
 decrypted data

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@...ux.ibm.com>
> Signed-off-by: Yael Tzur <yaelt@...gle.com>

Thanks,  Yael.

This patch is now queued in the #next-integrity-testing branch.

-- 
thanks,

Mimi