From: Petr Vorel <pvorel@suse.cz>
To: Ken Goldman <kgold@linux.ibm.com>
Cc: Linux Integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH 3/6] ima-evm-utils: When using the IBM TSS, link in its library
Date: Wed, 7 Oct 2020 14:25:18 +0200 [thread overview]
Message-ID: <20201007122518.GB9829@dell5510> (raw)
In-Reply-To: <f3b8356f-6476-5b1c-5faa-9b0dcd45d7dc@linux.ibm.com>
Hi Ken,
...
> > > diff --git a/src/Makefile.am b/src/Makefile.am
> > > index d6c779f..bf18caf 100644
> > > --- a/src/Makefile.am
> > > +++ b/src/Makefile.am
> > > @@ -26,6 +26,7 @@ if USE_PCRTSS
> > > evmctl_SOURCES += pcr_tss.c
> > > else
> > > evmctl_SOURCES += pcr_tsspcrread.c
> > > +evmctl_LDADD += -libmtss
> > > endif
> > But pcr_tsspcrread.c uses the binary (tsspcrread).
> The idea is to eliminate the calls to command line utilities that
> are not as stable as the TSS library. Patch 4/6 does that.
I'm sorry, I overlooked that.
> I'm a git newbie. I thought the idea was to do the patches as
> small pieces. Thus, this one does the autotools piece. Then
> the next one does the C code. Should they be combined?
I'd personally put it into the 4/6 patch (code change is small and it's related
to the code change).
> > pcr_tss.c uses TSS, but that's already covered:
> > ldd src/.libs/evmctl |grep tss
> > libtss2-rc.so.0 => /usr/lib64/libtss2-rc.so.0 (0x00007fb82514c000)
> > libtss2-esys.so.0 => /usr/lib64/libtss2-esys.so.0 (0x00007fb824eba000)
> > libtss2-sys.so.0 => /usr/lib64/libtss2-sys.so.0 (0x00007fb8244ba000)
> > libtss2-mu.so.0 => /usr/lib64/libtss2-mu.so.0 (0x00007fb824276000)
> > Thus I thing this patch is invalid. Or do I miss something obvious?
> There are two TSSes. This one's for the IBM TSS. Your traces are
> for the ESAPI (aka
Thanks for explanation.
Kind regards,
Petr
prev parent reply other threads:[~2020-10-07 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 22:28 [PATCH 3/6] ima-evm-utils: When using the IBM TSS, link in its library Ken Goldman
2020-10-06 15:07 ` Petr Vorel
2020-10-06 17:33 ` Ken Goldman
2020-10-06 17:58 ` Ken Goldman
2020-10-07 12:25 ` Petr Vorel [this message]
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=20201007122518.GB9829@dell5510 \
--to=pvorel@suse.cz \
--cc=kgold@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
/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