From: "Seiji Munetoh" <seiji.munetoh@gmail.com>
To: "Alexey Dobriyan" <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, kjhall@us.ibm.com,
tpmdd-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/2] tpm: bios log parsing fixes
Date: Mon, 22 May 2006 09:26:54 +0900 [thread overview]
Message-ID: <f02dbbe70605211726j51880184jfd01954fc202af9f@mail.gmail.com> (raw)
In-Reply-To: <20060518235744.GB5566@mipter.zuzino.mipt.ru>
2006/5/19, Alexey Dobriyan <adobriyan@gmail.com>:
> On Fri, May 19, 2006 at 08:29:07AM +0900, Seiji Munetoh wrote:
> > This patch fixes the BINARY output format to actual ACPI TCPA log
> > structure for any userland tool easily parse the binary data with
> > reference to TCG PC specification.
> Do you realize that you break backward compatibility? What was wrong
> with old format?
Yes I do, The problem is the binary output use get_event_name() to convert the
eventdata to ascii format. and the get_event_name() does not support all
eventdata types.Thus userspace application could not get the eventdata which
required to verify the PCRs in TPM.
I think actual ACPI log data is good for the binary output rather than current
unique binary format. It seems we are doing unnecessary transformation.
>
> > --- linux-2.6.17-rc4/drivers/char/tpm/tpm_bios.c
> > +++ linux-2.6.17-rc4-tpm/drivers/char/tpm/tpm_bios.c
> > @@ -275,53 +285,13 @@ static int get_event_name(char *dest, st
> >
> > static int tpm_binary_bios_measurements_show(struct seq_file *m, void
> > *v)
> > {
> > -
> > - char *eventname;
> > - char data[4];
> > - u32 help;
> > - int i, len;
> > struct tcpa_event *event = (struct tcpa_event *) v;
> > - unsigned char *event_entry =
> > - (unsigned char *) (v + sizeof(struct tcpa_event));
> > -
> > - eventname = kmalloc(MAX_TEXT_EVENT, GFP_KERNEL);
> > - if (!eventname) {
> > - printk(KERN_ERR "%s: ERROR - No Memory for event name\n ",
> > - __func__);
> > - return -ENOMEM;
> > - }
> > -
> > - /* 1st: PCR used is in little-endian format (4 bytes) */
> > - help = le32_to_cpu(event->pcr_index);
> > - memcpy(data, &help, 4);
> > - for (i = 0; i < 4; i++)
> > - seq_putc(m, data[i]);
> > -
> > - /* 2nd: SHA1 (20 bytes) */
> > - for (i = 0; i < 20; i++)
> > - seq_putc(m, event->pcr_value[i]);
> > + char *data = (char *) v;
> > + int i;
> >
> > - /* 3rd: event type identifier (4 bytes) */
> > - help = le32_to_cpu(event->event_type);
> > - memcpy(data, &help, 4);
> > - for (i = 0; i < 4; i++)
> > + for (i = 0;i < sizeof(struct tcpa_event) + event->event_size; i++)
> > seq_putc(m, data[i]);
> >
> > - len = 0;
> > -
> > - len += get_event_name(eventname, event, event_entry);
> > -
> > - /* 4th: filename <= 255 + \'0' delimiter */
> > - if (len > TCG_EVENT_NAME_LEN_MAX)
> > - len = TCG_EVENT_NAME_LEN_MAX;
> > -
> > - for (i = 0; i < len; i++)
> > - seq_putc(m, eventname[i]);
> > -
> > - /* 5th: delimiter */
> > - seq_putc(m, '\0');
> > -
> > - kfree(eventname);
> > return 0;
> > }
>
>
next prev parent reply other threads:[~2006-05-22 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 23:29 Seiji Munetoh
2006-05-18 23:57 ` Alexey Dobriyan
2006-05-22 0:26 ` Seiji Munetoh [this message]
2006-05-19 1:18 ` Kylene Jo Hall
2006-05-26 14:43 Seiji Munetoh
2006-05-26 14:43 ` Kylene Jo Hall
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=f02dbbe70605211726j51880184jfd01954fc202af9f@mail.gmail.com \
--to=seiji.munetoh@gmail.com \
--cc=adobriyan@gmail.com \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®