From: Kylene Jo Hall <kjhall@us.ibm.com>
To: Seiji Munetoh <seiji.munetoh@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: [PATCH 2/2] tpm: bios log parsing fixes
Date: Fri, 26 May 2006 09:43:59 -0500 [thread overview]
Message-ID: <1148654639.5317.205.camel@localhost.localdomain> (raw)
In-Reply-To: <1148654638.20195.41.camel@localhost.localdomain>
Ack'ed-by: Kylene Hall <kjhall@us.ibm.com>
On Fri, 2006-05-26 at 23:43 +0900, Seiji Munetoh wrote:
> This patch changes the binary output format to actual ACPI TCPA log
> structure since the current format does not contain all event-data
> information that need to verify the PCRs in TPM.
> tpm_binary_bios_measurements_show() uses get_event_name() to convert the
> binary event-data to ascii format, and puts them as binary. However, to
> verify the PCRs, the event-data must be a actual binary event-data used
> by SHA1 calc. in BIOS.
>
> So, I think actual ACPI TCPA log is good for this binary output format.
> That way, any userland tools easily parse this data with reference to
> TCG PC specification.
>
> Signed-off-by: Seiji Munetoh <seiji.munetoh@gmail.com>
> ---
>
> --- linux-2.6.17-rc4/drivers/char/tpm/tpm_bios.c 2006-05-16
> 09:33:06.000000000 +0900
> +++ linux-2.6.17-rc4-tpm/drivers/char/tpm/tpm_bios.c 2006-05-24
> 07:11:44.000000000 +0900
> @@ -275,53 +284,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-26 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 14:43 Seiji Munetoh
2006-05-26 14:43 ` Kylene Jo Hall [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-18 23:29 Seiji Munetoh
2006-05-18 23:57 ` Alexey Dobriyan
2006-05-22 0:26 ` Seiji Munetoh
2006-05-19 1:18 ` 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=1148654639.5317.205.camel@localhost.localdomain \
--to=kjhall@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seiji.munetoh@gmail.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
all inboxes | Powered by JetHome®