From: Jarkko Sakkinen <jarkko@kernel.org>
To: Nikolaus Voss <nv@vosn.de>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: encrypted: fix key instantiation with user-provided data
Date: Tue, 20 Sep 2022 08:06:15 +0300 [thread overview]
Message-ID: <YylKR1UQZGhN0+UW@kernel.org> (raw)
In-Reply-To: <20220919072317.E41421357@mail.steuer-voss.de>
On Fri, Sep 16, 2022 at 07:45:29AM +0200, Nikolaus Voss wrote:
> Commit cd3bc044af48 ("KEYS: encrypted: Instantiate key with user-provided
> decrypted data") added key instantiation with user provided decrypted data.
> The user data is hex-ascii-encoded but was just memcpy'ed to the binary buffer.
> Fix this to use hex2bin instead.
>
> Fixes: cd3bc044af48 ("KEYS: encrypted: Instantiate key with user-provided decrypted data")
> Cc: stable <stable@kernel.org>
> Signed-off-by: Nikolaus Voss <nikolaus.voss@haag-streit.com>
> ---
> security/keys/encrypted-keys/encrypted.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/security/keys/encrypted-keys/encrypted.c b/security/keys/encrypted-keys/encrypted.c
> index e05cfc2e49ae..1e313982af02 100644
> --- a/security/keys/encrypted-keys/encrypted.c
> +++ b/security/keys/encrypted-keys/encrypted.c
> @@ -627,7 +627,7 @@ static struct encrypted_key_payload *encrypted_key_alloc(struct key *key,
> pr_err("encrypted key: instantiation of keys using provided decrypted data is disabled since CONFIG_USER_DECRYPTED_DATA is set to false\n");
> return ERR_PTR(-EINVAL);
> }
> - if (strlen(decrypted_data) != decrypted_datalen) {
> + if (strlen(decrypted_data) != decrypted_datalen * 2) {
This looks wrong. What does cap decrypted_data, and why strnlen()
is not used?
> pr_err("encrypted key: decrypted data provided does not match decrypted data length provided\n");
Using pr_err() is probably wrong here and has different prefix
than elsewhere in the file (also most of other uses of pr_err()
are wrong apparently). Nothing bad is really happening.
And who does make any sense of that error message anyway?
For one, I don't understand it.
> return ERR_PTR(-EINVAL);
> }
> @@ -791,8 +791,8 @@ static int encrypted_init(struct encrypted_key_payload *epayload,
> ret = encrypted_key_decrypt(epayload, format, hex_encoded_iv);
> } else if (decrypted_data) {
> get_random_bytes(epayload->iv, ivsize);
> - memcpy(epayload->decrypted_data, decrypted_data,
> - epayload->decrypted_datalen);
> + ret = hex2bin(epayload->decrypted_data, decrypted_data,
> + epayload->decrypted_datalen);
> } else {
> get_random_bytes(epayload->iv, ivsize);
> get_random_bytes(epayload->decrypted_data, epayload->decrypted_datalen);
> --
> 2.34.1
>
BR, Jarkko
next prev parent reply other threads:[~2022-09-20 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 5:45 [PATCH] KEYS: encrypted: fix key instantiation with user-provided data Nikolaus Voss
2022-09-20 5:06 ` Jarkko Sakkinen [this message]
2022-09-20 7:58 ` Nikolaus Voss
2022-09-21 17:51 ` Jarkko Sakkinen
2022-09-28 13:03 ` Nikolaus Voss
2022-09-20 14:43 ` Mimi Zohar
2022-09-20 16:23 ` Nikolaus Voss
2022-09-20 22:53 ` Mimi Zohar
2022-09-21 7:24 ` Nikolaus Voss
2022-09-21 12:49 ` Mimi Zohar
2022-09-28 12:08 ` Nikolaus Voss
2022-09-28 16:33 ` Mimi Zohar
2022-10-05 10:04 ` Nikolaus Voss
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=YylKR1UQZGhN0+UW@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.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=nv@vosn.de \
--cc=serge@hallyn.com \
--cc=zohar@linux.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.