From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Vitaly Chikunov <vt@altlinux.org>, linux-integrity@vger.kernel.org
Subject: Re: [ima-evm-utils: PATCH 5/5] ima-evm-utils: travis: openssl gost engine
Date: Thu, 13 Aug 2020 14:15:45 -0400 [thread overview]
Message-ID: <93793b105fc2945435e3c26a6f74eee28ae03e0f.camel@linux.ibm.com> (raw)
In-Reply-To: <20200812130548.GB4994@gacrux.arch.suse.de>
On Wed, 2020-08-12 at 15:05 +0200, Petr Vorel wrote:
> Hi Mimi, Vitaly,
>
> ...
> > > I prototype docker based Travis [1] (still WIP). It tests various distros,
> > > including cross-compilation, using also clang, even one build with musl (Alpine
> > > distro). But there are many failures.
> > > The biggest problem is with ibmswtpm2 [2], which contain tpm_server binary. This
> > > project is not packaged in distros, compiles only with gcc (no clang, I tested
> > > versions 1332 and 1637) and ignore CFLAGS and LDFLAGS settings. It doesn't even
> > > have git repository (the one on sourceforge is empty).
> > > We could simply patch this file, but I'm not going to do it.
> > > I guess I just skip tpm_server dependency for all non-native projects.
> > > I also need always install gcc even clang is going to be used due tpm_server.
> > Agreed, getting docker/travis working is independent of tpm_server.
> > Without a software TPM, the boot_aggregate test will be skipped. For
> > now, until we can straighten this out, I would modify "make check" to
> > run the other tests (e.g. make check TESTS="ima_hash.test
> > sign_verify.test").
> Yes, specifying tests to be tested is an option. But if skipping the compilation
> for non-native builds works (e.g. tests which don't specify $VARIANT), I'd go
> this way. That help us not having to remember to update tests for non-native
> builds (once the new ones are added).
Sure. libtmps/swtpm could be installed in lieu of the ibmswtpm2.
Sample directions for using it are here:
https://github.com/stefanberger/swtpm/wiki/Using-the-IBM-TSS-with-swtpm
.
thanks,
Mimi
next prev parent reply other threads:[~2020-08-13 18:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 18:24 [ima-evm-utils: PATCH 0/5] initial travis support Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 1/5] ima-evm-utils: travis: define travis.yml Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 2/5] ima-evm-utils: travis: download, compile, and install a swTPM Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 3/5] ima-evm-utils: travis: dependency on TSS for initializing software TPM Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 4/5] ima-evm-utils: travis: support tpm2-tss Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 5/5] ima-evm-utils: travis: openssl gost engine Mimi Zohar
2020-07-31 18:56 ` Vitaly Chikunov
2020-07-31 20:18 ` Petr Vorel
2020-07-31 20:26 ` Vitaly Chikunov
2020-07-31 20:40 ` Petr Vorel
2020-07-31 21:06 ` Vitaly Chikunov
2020-07-31 22:32 ` Mimi Zohar
2020-08-03 3:09 ` Mimi Zohar
2020-08-03 13:07 ` Petr Vorel
2020-08-03 14:29 ` Mimi Zohar
2020-08-03 16:46 ` Petr Vorel
2020-08-03 17:16 ` Mimi Zohar
2020-08-04 7:22 ` Petr Vorel
2020-08-04 7:54 ` Petr Vorel
2020-08-04 13:23 ` Mimi Zohar
2020-08-05 9:42 ` Petr Vorel
2020-08-05 13:31 ` Mimi Zohar
2020-08-05 16:23 ` Vitaly Chikunov
2020-08-05 16:18 ` Vitaly Chikunov
2020-08-11 17:33 ` Petr Vorel
2020-08-11 22:04 ` Mimi Zohar
2020-08-12 13:05 ` Petr Vorel
2020-08-13 18:15 ` Mimi Zohar [this message]
2020-08-13 18:28 ` Petr Vorel
2020-08-13 20:11 ` Mimi Zohar
2020-08-03 16:32 ` Vitaly Chikunov
2020-08-03 16:36 ` Petr Vorel
2020-08-03 17:26 ` Mimi Zohar
2020-08-03 18:42 ` Vitaly Chikunov
2020-08-03 2:53 ` Mimi Zohar
2020-08-03 13:11 ` Petr Vorel
2020-08-03 14:33 ` Mimi Zohar
2020-08-04 12:05 ` [ima-evm-utils: PATCH v1 " Mimi Zohar
2020-08-04 14:45 ` Vitaly Chikunov
2020-08-04 18:11 ` Mimi Zohar
2020-07-31 20:19 ` [ima-evm-utils: PATCH 0/5] initial travis support Petr Vorel
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=93793b105fc2945435e3c26a6f74eee28ae03e0f.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=vt@altlinux.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;
as well as URLs for NNTP newsgroup(s).