From: Denis Kenzior <denkenz@gmail.com>
To: Vitaly Chikunov <vt@altlinux.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Howells <dhowells@redhat.com>,
Mimi Zohar <zohar@linux.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 05/10] X.509: parse public key parameters from x509 for akcipher
Date: Tue, 26 Mar 2019 11:14:37 -0500 [thread overview]
Message-ID: <e302ad90-98c7-1e82-4d49-8ad214fd6ee7@gmail.com> (raw)
In-Reply-To: <20190326125842.24110-6-vt@altlinux.org>
Hi Vitaly,
On 03/26/2019 07:58 AM, Vitaly Chikunov wrote:
> Some public key algorithms (like EC-DSA) keep in parameters field
> important data such as digest and curve OIDs (possibly more for
> different EC-DSA variants). Thus, just setting a public key (as
> for RSA) is not enough.
>
> Append parameters into the key stream for akcipher_set_{pub,priv}_key.
> Appended data is: (u32) algo OID, (u32) parameters length, parameters
> data.
>
> This does not affect current akcipher API nor RSA ciphers (they could
> ignore it). Idea of appending parameters to the key stream is by Herbert
> Xu.
>
> Cc: David Howells <dhowells@redhat.com>
> Cc: keyrings@vger.kernel.org
> Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> ---
> crypto/asymmetric_keys/asym_tpm.c | 43 ++++++++++++++++--
> crypto/asymmetric_keys/public_key.c | 72 ++++++++++++++++++++++++-------
> crypto/asymmetric_keys/x509.asn1 | 2 +-
> crypto/asymmetric_keys/x509_cert_parser.c | 31 +++++++++++++
> crypto/testmgr.c | 24 +++++++++--
> crypto/testmgr.h | 5 +++
> include/crypto/akcipher.h | 18 ++++----
> include/crypto/public_key.h | 4 ++
> 8 files changed, 168 insertions(+), 31 deletions(-)
>
> diff --git a/crypto/asymmetric_keys/asym_tpm.c b/crypto/asymmetric_keys/asym_tpm.c
> index 402fc34ca044..d95d7ec50e5a 100644
> --- a/crypto/asymmetric_keys/asym_tpm.c
> +++ b/crypto/asymmetric_keys/asym_tpm.c
> @@ -395,6 +395,12 @@ static int determine_akcipher(const char *encoding, const char *hash_algo,
> return -ENOPKG;
> }
>
> +static u8 *tpm_pack_u32(u8 *dst, u32 val)
> +{
> + memcpy(dst, &val, sizeof(val));
> + return dst + sizeof(val);
> +}
> +
> /*
> * Query information about a key.
> */
> @@ -407,6 +413,7 @@ static int tpm_key_query(const struct kernel_pkey_params *params,
> struct crypto_akcipher *tfm;
> uint8_t der_pub_key[PUB_KEY_BUF_SIZE];
> uint32_t der_pub_key_len;
> + u8 *pkey, *ptr;
> int len;
>
> /* TPM only works on private keys, public keys still done in software */
> @@ -421,7 +428,16 @@ static int tpm_key_query(const struct kernel_pkey_params *params,
> der_pub_key_len = derive_pub_key(tk->pub_key, tk->pub_key_len,
> der_pub_key);
>
> - ret = crypto_akcipher_set_pub_key(tfm, der_pub_key, der_pub_key_len);
> + pkey = kmalloc(der_pub_key_len + sizeof(u32) * 2, GFP_KERNEL);
> + if (!pkey)
> + goto error_free_tfm;
> + memcpy(pkey, der_pub_key, der_pub_key_len);
> + ptr = pkey + der_pub_key_len;
> + /* Set dummy parameters to satisfy set_pub_key ABI. */
> + ptr = tpm_pack_u32(ptr, 0); /* algo */
> + ptr = tpm_pack_u32(ptr, 0); /* parameter length */
> +
Why not do all of this inside derive_pub_key? The only reason for that
function is to take a TPM-blob formatted public key and convert it to
ASN.1 format understood by crypto_akcipher_set_pub_key. So if you're
changing the format, might as well update that function.
> + ret = crypto_akcipher_set_pub_key(tfm, pkey, der_pub_key_len);
> if (ret < 0)
> goto error_free_tfm;
>
> @@ -440,6 +456,7 @@ static int tpm_key_query(const struct kernel_pkey_params *params,
>
> ret = 0;
> error_free_tfm:
> + kfree(pkey);
> crypto_free_akcipher(tfm);
> pr_devel("<==%s() = %d\n", __func__, ret);
> return ret;
> @@ -460,6 +477,7 @@ static int tpm_key_encrypt(struct tpm_key *tk,
> struct scatterlist in_sg, out_sg;
> uint8_t der_pub_key[PUB_KEY_BUF_SIZE];
> uint32_t der_pub_key_len;
> + u8 *pkey, *ptr;
> int ret;
>
> pr_devel("==>%s()\n", __func__);
> @@ -475,7 +493,15 @@ static int tpm_key_encrypt(struct tpm_key *tk,
> der_pub_key_len = derive_pub_key(tk->pub_key, tk->pub_key_len,
> der_pub_key);
>
> - ret = crypto_akcipher_set_pub_key(tfm, der_pub_key, der_pub_key_len);
> + pkey = kmalloc(der_pub_key_len + sizeof(u32) * 2, GFP_KERNEL);
> + if (!pkey)
> + goto error_free_tfm;
> + memcpy(pkey, der_pub_key, der_pub_key_len);
> + ptr = pkey + der_pub_key_len;
> + ptr = tpm_pack_u32(ptr, 0); /* algo */
> + ptr = tpm_pack_u32(ptr, 0); /* parameter length */
> +
Same comment as above
> + ret = crypto_akcipher_set_pub_key(tfm, pkey, der_pub_key_len);
> if (ret < 0)
> goto error_free_tfm;
>
> @@ -500,6 +526,7 @@ static int tpm_key_encrypt(struct tpm_key *tk,
>
> akcipher_request_free(req);
> error_free_tfm:
> + kfree(pkey);
> crypto_free_akcipher(tfm);
> pr_devel("<==%s() = %d\n", __func__, ret);
> return ret;
> @@ -748,6 +775,7 @@ static int tpm_key_verify_signature(const struct key *key,
> char alg_name[CRYPTO_MAX_ALG_NAME];
> uint8_t der_pub_key[PUB_KEY_BUF_SIZE];
> uint32_t der_pub_key_len;
> + u8 *pkey, *ptr;
> int ret;
>
> pr_devel("==>%s()\n", __func__);
> @@ -770,7 +798,15 @@ static int tpm_key_verify_signature(const struct key *key,
> der_pub_key_len = derive_pub_key(tk->pub_key, tk->pub_key_len,
> der_pub_key);
>
> - ret = crypto_akcipher_set_pub_key(tfm, der_pub_key, der_pub_key_len);
> + pkey = kmalloc(der_pub_key_len + sizeof(u32) * 2, GFP_KERNEL);
> + if (!pkey)
> + goto error_free_tfm;
> + memcpy(pkey, der_pub_key, der_pub_key_len);
> + ptr = pkey + der_pub_key_len;
> + ptr = tpm_pack_u32(ptr, 0); /* algo */
> + ptr = tpm_pack_u32(ptr, 0); /* parameter length */
> +
And here
> + ret = crypto_akcipher_set_pub_key(tfm, pkey, der_pub_key_len);
> if (ret < 0)
> goto error_free_tfm;
>
> @@ -792,6 +828,7 @@ static int tpm_key_verify_signature(const struct key *key,
>
> akcipher_request_free(req);
> error_free_tfm:
> + kfree(pkey);
> crypto_free_akcipher(tfm);
> pr_devel("<==%s() = %d\n", __func__, ret);
> if (WARN_ON_ONCE(ret > 0))
Regards,
-Denis
next prev parent reply other threads:[~2019-03-26 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:58 [PATCH v8 00/10] crypto: add EC-RDSA (GOST 34.10) algorithm Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 01/10] crypto: akcipher - default implementations for request callbacks Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 02/10] crypto: rsa - unimplement sign/verify for raw RSA backends Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 03/10] crypto: akcipher - new verify API for public key algorithms Vitaly Chikunov
2019-03-26 16:00 ` Denis Kenzior
2019-03-26 12:58 ` [PATCH v8 04/10] KEYS: do not kmemdup digest in {public,tpm}_key_verify_signature Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 05/10] X.509: parse public key parameters from x509 for akcipher Vitaly Chikunov
2019-03-26 16:14 ` Denis Kenzior [this message]
2019-03-26 12:58 ` [PATCH v8 06/10] crypto: Kconfig - create Public-key cryptography section Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 07/10] crypto: ecc - make ecc into separate module Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 08/10] crypto: ecrdsa - add EC-RDSA (GOST 34.10) algorithm Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 09/10] crypto: ecrdsa - add EC-RDSA test vectors to testmgr Vitaly Chikunov
2019-03-26 12:58 ` [PATCH v8 10/10] integrity: support EC-RDSA signatures for asymmetric_verify Vitaly Chikunov
2019-03-27 18:10 ` Mimi Zohar
2019-03-27 20:14 ` Vitaly Chikunov
2019-03-27 20:21 ` Mimi Zohar
2019-03-28 6:16 ` Vitaly Chikunov
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=e302ad90-98c7-1e82-4d49-8ad214fd6ee7@gmail.com \
--to=denkenz@gmail.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vt@altlinux.org \
--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 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).