All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
	linux-crypto@vger.kernel.org,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	James Morris <jmorris@namei.org>,
	David Safford <safford@watson.ibm.com>,
	Rajiv Andrade <srajiv@linux.vnet.ibm.com>,
	Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH v1.5 4/5] keys: add new trusted key-type
Date: Wed, 01 Dec 2010 17:48:30 +0000	[thread overview]
Message-ID: <9594.1291225710@redhat.com> (raw)
In-Reply-To: <1290552635-3356-5-git-send-email-zohar@linux.vnet.ibm.com>

Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:

> +static int TSS_sha1(const unsigned char *data, const unsigned int datalen,
> +		    unsigned char *digest)

You seem to have made a bunch of integer length parameters 'const'.  Why?  I
was suggesting making them size_t, not const.

I was suggesting making the data pointers const.

> +	if (!ret)
> +		TSS_rawhmac(digest, key, keylen, SHA1_DIGEST_SIZE,
> +			    paramdigest, TPM_NONCE_SIZE, h1,
> +			    TPM_NONCE_SIZE, h2, 1, &c, 0, 0);

TSS_rawhmac() can return an error.

> +	ret = trusted_tpm_send(TPM_ANY_NUM, tb->data, sizeof tb->data);
> +	memcpy(buf, tb->data + TPM_GETRANDOM_SIZE, len);

trusted_tpm_send() won't fail?

> +static int my_get_random(unsigned char *buf, int len)
> +{
> +	struct tpm_buf *tb;
> +	int ret;
> +
> +	tb = kzalloc(sizeof *tb, GFP_KERNEL);
> +	if (!tb)
> +		return -ENOMEM;
> +	ret = tpm_get_random(tb, buf, len);

Isn't is it pointless to use kzalloc() rather than kmalloc()?

> +	my_get_random(hash, SHA1_DIGEST_SIZE);
> +	return tpm_pcr_extend(TPM_ANY_NUM, pcrnum, hash) ? -EINVAL : 0;

my_get_random() won't fail?

> +	ret = TSS_rawhmac(s->secret, key, SHA1_DIGEST_SIZE, TPM_NONCE_SIZE,
> +			  enonce, TPM_NONCE_SIZE, ononce, 0, 0);
> +	return ret;

These can be merged.

> +static int oiap(struct tpm_buf *tb, uint32_t *handle, unsigned char *nonce)
> +{
> +	int ret;
> +
> +	INIT_BUF(tb);
> +	store16(tb, TPM_TAG_RQU_COMMAND);
> +	store32(tb, TPM_OIAP_SIZE);
> +	store32(tb, TPM_ORD_OIAP);
> +	ret = trusted_tpm_send(TPM_ANY_NUM, tb->data, MAX_BUF_SIZE);
> +	if (ret < 0)
> +		return ret;
> +
> +	*handle = LOAD32(tb->data, TPM_DATA_OFFSET);
> +	memcpy(nonce, &tb->data[TPM_DATA_OFFSET + sizeof(uint32_t)],
> +	       TPM_NONCE_SIZE);
> +	return ret;
> +}

If you don't need to return ret specifically, returning 0 would be more
efficient.

> +	ret = TSS_checkhmac1(tb->data, ordinal, td->nonceodd, sess.secret,
> +			     SHA1_DIGEST_SIZE, storedsize, TPM_DATA_OFFSET, 0,
> +			     0);
> +
> +	/* copy the returned blob to caller */
> +	memcpy(blob, tb->data + TPM_DATA_OFFSET, storedsize);
> +	*bloblen = storedsize;

Don't do that if TSS_checkhmac1() fails.

> +	TSS_authhmac(authdata1, keyauth, TPM_NONCE_SIZE,
> +		     enonce1, nonceodd, cont, sizeof(uint32_t),
> +		     &ordinal, bloblen, blob, 0, 0);

TSS_authhmac() is called several times without checking for errors.

> +	ret = TSS_checkhmac2(tb->data, ordinal, nonceodd,
> +			     keyauth, SHA1_DIGEST_SIZE,
> +			     blobauth, SHA1_DIGEST_SIZE,
> +			     sizeof(uint32_t), TPM_DATA_OFFSET,
> +			     *datalen, TPM_DATA_OFFSET + sizeof(uint32_t), 0,
> +			     0);
> +	if (ret < 0)
> +		pr_info("trusted_key: TSS_checkhmac2 failed (%d)\n", ret);
> +	memcpy(data, tb->data + TPM_DATA_OFFSET + sizeof(uint32_t), *datalen);
> +	return ret;

Don't do the memcpy() if TSS_checkhmac2() fails.

> +	ret = tpm_unseal(tb, o->keyhandle, o->keyauth, p->blob, p->blob_len,
> +			 o->blobauth, p->key, &p->key_len);
> +	/* pull migratable flag out of sealed key */
> +	p->migratable = p->key[--p->key_len];

Don't do that if tpm_unseal() fails.

> +static const match_table_t key_tokens = {
> +	{Opt_new, "new"},
> +	{Opt_load, "load"},
> +	{Opt_update, "update"},
> +	{Opt_keyhandle, "keyhandle=%s"},
> +	{Opt_keyauth, "keyauth=%s"},
> +	{Opt_blobauth, "blobauth=%s"},
> +	{Opt_pcrinfo, "pcrinfo=%s"},
> +	{Opt_pcrlock, "pcrlock=%s"},
> +	{Opt_migratable, "migratable=%s"},
> +	{Opt_err, NULL}

Spaces after { and before }.  I'd also suggest using tabs to align the strings
vertically, but that's up to you.

> +	p = kzalloc(sizeof *p, GFP_KERNEL);
> +
> +	/* migratable by default */
> +	p->migratable = 1;

NAK!  p might be NULL.

David

  reply	other threads:[~2010-12-01 18:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 22:50 [PATCH v1.5 0/5] keys: trusted and encrypted keys Mimi Zohar
2010-11-23 22:50 ` [PATCH v1.5 2/5] tpm: add module_put wrapper Mimi Zohar
2010-11-24  2:19   ` Serge Hallyn
2010-11-23 22:50 ` [PATCH v1.5 4/5] keys: add new trusted key-type Mimi Zohar
2010-12-01 17:48   ` David Howells [this message]
2010-12-01 21:18     ` David Safford
2010-11-23 23:43 ` [PATCH v1.5 1/5] lib: hex2bin converts ascii hexadecimal string to binary Mimi Zohar
2010-11-23 23:54 ` [PATCH v1.5 3/5] key: add tpm_send command Mimi Zohar
2010-11-24  2:32   ` Serge Hallyn
2010-11-24 12:46     ` David Safford
2010-11-24 14:59       ` Serge Hallyn
2010-11-24 16:31         ` David Safford
2010-11-30 14:32     ` David Howells
2010-11-30 15:22       ` David Safford
2010-11-24 16:21 ` [PATCH v1.5 5/5] keys: add new key-type encrypted Mimi Zohar
2010-11-28 21:56 ` [PATCH v1.5 0/5] keys: trusted and encrypted keys James Morris
     [not found] ` <1290556535.2604.16.camel@localhost.localdomain>
2010-12-03 13:42   ` [PATCH v1.5 5/5] keys: add new key-type encrypted David Howells
2010-12-07 22:48     ` Mimi Zohar
2010-12-08 10:54       ` David Howells

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=9594.1291225710@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=safford@watson.ibm.com \
    --cc=srajiv@linux.vnet.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    --cc=zohar@us.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.