All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Mikhail Novosyolov <m.novosyolov@rosalinux.ru>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	Wartan Hachaturow <wart@debian.org>,
	linux-integrity@vger.kernel.org,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: Re: [PATCH ima-evm-utils] boot_aggregate.test: Skip if CONFIG_IMA not enabled
Date: Tue, 27 Oct 2020 21:01:35 +0100	[thread overview]
Message-ID: <20201027200135.GB7513@x230> (raw)
In-Reply-To: <bd321cc1-260c-0ed2-2143-dac2b7489903@rosalinux.ru>

Hi all,

...
> > Mikhail, my mistake.  Thank you for the correction!   Testing the
> > libressl changes should be a lot easier now.  Please remember to
> > include a distro travis.yml example.

> What do you mean? Do you mean adding testing of building ima-evm-utils against LibreSSL?
Yes, I understand Mimi wants this.

> Which environment is used there and which ones are available? There are not many dsitros where LibreSSL is pre-packaged [1], in many of them it is not updated often enough.
Look at the supported distros in travis/ in next or next-testing branch.
Could you use some bleeding edge distro (Tumbleweed or Fedora?)
You could handl LibreSSL vs. openSSL with variable, similarly like IBM TSS and
Intel TSS are handled (with $TSS variable).

> I would choose either ROSA where I myself maintain LibreSSL and ima-evm-utils or Arch Linux, is at least Arch Linux available in CI/CD environment?
> Won't we have to deal with often breakages of other parts of the rolling Arch Linux?

> Also, I can just build LibreSSL from source in any available distro, e.g. Ubuntu, but the pipeline will take a lot more time.
Please use distro package. Not only it's faster (as you noted), but it also
covers more users (IMHO most of the people use distro package, not a git version).

> How do we better deal with it?

Kind regards,
Petr

> [1] https://repology.org/project/libressl/versions

  reply	other threads:[~2020-10-27 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 20:08 [PATCH ima-evm-utils] boot_aggregate.test: Skip if CONFIG_IMA not enabled Petr Vorel
2020-10-19 23:10 ` Mimi Zohar
2020-10-20 18:02   ` Petr Vorel
2020-10-27 16:06     ` Mimi Zohar
2020-10-27 18:51       ` Mikhail Novosyolov
2020-10-27 19:06         ` Mimi Zohar
2020-10-27 19:29           ` Mikhail Novosyolov
2020-10-27 20:01             ` Petr Vorel [this message]
2020-10-27 18:49     ` Tyler Hicks
2020-10-27 18:57       ` Mikhail Novosyolov
2020-10-23 12:46   ` Mimi Zohar

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=20201027200135.GB7513@x230 \
    --to=petr.vorel@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=m.novosyolov@rosalinux.ru \
    --cc=wart@debian.org \
    --cc=zohar@linux.ibm.com \
    --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.