From: Peter Robinson <pbrobinson@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: sandbox TPM
Date: Sun, 29 Aug 2021 11:53:02 +0100 [thread overview]
Message-ID: <CALeDE9MAuiHDqC83+dLZd6DUzN0Xk9ePP0wZ7PegaRtuTjgg4Q@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ1eddQ7S+Cr6YAqQzL+DSxY5v7ExsZWmdbrBK1jRjdtBw@mail.gmail.com>
On Sat, Aug 28, 2021 at 10:19 PM Simon Glass <sjg@chromium.org> wrote:
>
> Hi Heinrich,
>
> On Sat, 28 Aug 2021 at 06:18, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > The current TPM emulation in drivers/tpm/tpm(2)_tis_sandbox.c is not
> > spec compliant.
>
> Do you mean it is incomplete or that it has bugs? If it is incomplete,
> what is needed by U-Boot?
>
> >
> > A TPM emulation as UNIX socket exists with
> > https://github.com/stefanberger/swtpm.git. QEMU already uses this emulator.
> >
> > Couldn't the sandbox do the same? I think this is the fastest way to get
> > a compliant sandbox TPM.
>
> Well we could if we need it. Are you sure it is a good idea? There is
> a lot of code there. Are you thinking it would be copied into the
> U-Boot tree and kept in sync with a script, perhaps? Presumably the
> project would accept changes we need?
qemu doesn't copy it in, why can't it just run independently as part
of the CI process? The rust TPM2 bindings do that here:
https://github.com/parallaxsecond/rust-tss-esapi/blob/main/tss-esapi/tests/all-fedora.sh#L13
next prev parent reply other threads:[~2021-08-29 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 12:18 sandbox TPM Heinrich Schuchardt
2021-08-28 21:19 ` Simon Glass
2021-08-29 10:53 ` Peter Robinson [this message]
2021-08-30 6:10 ` Ilias Apalodimas
2021-08-30 7:34 ` Heinrich Schuchardt
2021-09-02 16:41 ` Simon Glass
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=CALeDE9MAuiHDqC83+dLZd6DUzN0Xk9ePP0wZ7PegaRtuTjgg4Q@mail.gmail.com \
--to=pbrobinson@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.