From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Vitaly Chikunov <vt@altlinux.org>,
linux-integrity@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [PATCH ima-evm-utils] release feature discussion [renamed from Drop empty NEWS file]
Date: Thu, 23 Jul 2020 14:04:40 -0400 [thread overview]
Message-ID: <1595527480.5211.185.camel@linux.ibm.com> (raw)
In-Reply-To: <20200723170556.GA20782@dell5510>
On Thu, 2020-07-23 at 19:05 +0200, Petr Vorel wrote:
> Hi Mimi,
>
> ...
> > > > Also, having docker based travis setup helps to test build against other distros
> > > > (we have it in LTP).
>
> > The existing travis.yml is a first attempt at using travis. (Hint:
> > help with cleaning it up would be much appreciated.) Should this
> > travis.yml be included now in 1.3.1 or deferred to 1.3.2? Let's sync
> > up on what should be included when. Additional suggestions are
> > welcome.
>
> > 1.3.1 release (~1 week):
> > - minor fixes
>
> > Proposed 1.3.2 features (~3 months):
> > - Travis integration
> > - Support providing the TPM 2.0 PCRs as a file (--pcrs option).
> > - Walking the TPM 2.0 event log as the basis for calculating the
> > "boot_aggregate".
>
> Thank you for sharing your roadmap. I'd vote for sooner include (it's not set
> in the stone, it can be changed later :)), but up to you.
>
> Not sure if I have enough time to significantly help with Travis, I'll try.
> That docker based testing is nice, because it's a testing on real distro.
Thanks, Petr. You've provided so much help, support, and guidance
already. We know a lot of companies are using the Integrity
subsystem. Some are even actively contributing to it. They should
realize the more time I need to spend on ima-evm-utils, means the less
time I have for reviewing and upstreaming kernel patches. Hopefully
they're listening and will step up to helping improve ima-evm-utils as
well. I can't be any blunter than that. Let's see what happens. :)
Mimi
next prev parent reply other threads:[~2020-07-23 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 11:47 [PATCH ima-evm-utils] Drop empty NEWS file Petr Vorel
2020-07-22 14:27 ` Mimi Zohar
2020-07-22 14:45 ` Vitaly Chikunov
2020-07-22 14:50 ` Petr Vorel
2020-07-22 15:31 ` Mimi Zohar
2020-07-23 11:18 ` Mimi Zohar
2020-07-23 11:54 ` Petr Vorel
2020-07-23 12:07 ` Mimi Zohar
2020-07-23 12:29 ` Petr Vorel
2020-07-23 14:04 ` Vitaly Chikunov
2020-07-23 14:30 ` [PATCH ima-evm-utils] release feature discussion [renamed from Drop empty NEWS file] Mimi Zohar
2020-07-23 17:05 ` Petr Vorel
2020-07-23 18:04 ` Mimi Zohar [this message]
2020-07-24 5:28 ` [PATCH ima-evm-utils] Drop empty NEWS file Petr Vorel
2020-07-22 14:45 ` 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=1595527480.5211.185.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=vt@altlinux.org \
--cc=zohar@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 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.