qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: chrisw@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V7 5/9] Support for BIOS interrupt handler
Date: Wed, 31 Aug 2011 22:03:24 +0200	[thread overview]
Message-ID: <20110831200324.GB18881@zapo> (raw)
In-Reply-To: <20110831195858.GA18881@zapo>

On Wed, Aug 31, 2011 at 09:58:58PM +0200, Edgar E. Iglesias wrote:
> On Wed, Aug 31, 2011 at 03:45:45PM -0400, Stefan Berger wrote:
> > This patch implements the TCG BIOS interrupt handler 1ah. It is for
> > example used by trusted grub.
> > 
> > This patch adds an implementation of SHA1 (following NIST specs., IETF RFC 3147
> > and Wikipedia) for speeding up measurements of code. Trusted Grub for example
> > makes use of this interface and measures (calculates SHA1) of the Linux kernel
> > and initrd. Those files can be rather large and hunting their bytes through
> > the TIS interface as part of the int handler commands invoked by trusted grub
> > does take quite some time due to the many vmexits the interface is creating
> > (one per byte).
> > 
> > There is also a threshold for the size of data to hash (100k) below which
> > the TPM is used and above the internal faster SHA1 algorithm is used.
> 
> Hi Stefan,
> 
> A question:
> Is there a reason for not reusing the SHA1 implementation from other libraries,
> like OpenSSL?
> 
> I've got a couple of cryptographic device models on my end (some of them
> that I may contribute at some point) that will need the various SHA hashes
> and other ciphers.
> 
> In my case, there might be tons of data beeing hashed and when available,
> it would be nice to be able to use cryptographic hw acceleration which
> may be provided by OpenSSL engines. Or even, just heavily optimized
> assembly versions of them.

Woops, maybe this particular piece of code was not for QEMU proper...

Cheers

  reply	other threads:[~2011-08-31 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 19:45 [Qemu-devel] [PATCH V7 0/9] Add TPM support to SeaBIOS Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 1/9] Add an implementation of a TPM TIS driver Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 2/9] Provide ACPI SSDT table for TPM device + S3 resume support Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 3/9] Add public get_rsdp function Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 4/9] Implementation of the TCG BIOS extensions Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 5/9] Support for BIOS interrupt handler Stefan Berger
2011-08-31 19:58   ` Edgar E. Iglesias
2011-08-31 20:03     ` Edgar E. Iglesias [this message]
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 6/9] Add measurement code to the BIOS Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 7/9] Add a menu for TPM control Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 8/9] Support for Qemu-provided measurements Stefan Berger
2011-08-31 19:45 ` [Qemu-devel] [PATCH V7 9/9] Optional tests for the TIS interface Stefan Berger

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=20110831200324.GB18881@zapo \
    --to=edgar.iglesias@gmail.com \
    --cc=chrisw@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=stefanb@linux.vnet.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).