From: Russell Coker <russell@coker.com.au>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: William Roberts <bill.c.roberts@gmail.com>,
Laurent Bigonville <bigon@debian.org>,
SElinux list <selinux@vger.kernel.org>,
Ondrej Mosnacek <omosnace@redhat.com>,
Paul Moore <paul@paul-moore.com>
Subject: Re: [PATCH] selinux-testsuite: update to work on Debian
Date: Thu, 07 May 2020 02:37:11 +1000 [thread overview]
Message-ID: <3838641.zh4Wi6GlAV@liv> (raw)
In-Reply-To: <CAEjxPJ452zaoFwy++cKqh_Ap2rM1ezEZN83mBhN4ndHHaQ4q5Q@mail.gmail.com>
On Thursday, 7 May 2020 1:50:46 AM AEST Stephen Smalley wrote:
> on that running instance, but not to specify custom kernel parameters
> initially or to reboot the system before proceeding with further
> commands (if anyone knows differently, speak up). We'd have to get to
> the point where enabling SELinux in Debian is possible without
> requiring a reboot at all. And then we'd have to wait for that
> support to find its way into one of the Ubuntu images supported by
> travis-ci. Might be easier to just get travis-ci to support Fedora or
> CentOS images in the first place. Regardless, allowing the testsuite
> to be run by users of other distributions is worthwhile IMHO.
In the past there hasn't been much demand for a smoother installation process.
If you are setting up a traditional Unix server system the Debian SE Linux
installation thing doesn't make things much more difficult. Past complaints
about it have been more about an imagined difficulty of using SE Linux and have
ended when I showed and wrote about how to do it (one time I showed
screenshots of the process in an LCA lightning talk and didn't have problems
with time).
I don't think that the people who maintain the Debian installation related
packages would have a great objection to adding SE Linux features, although it
might take a bit of time for it to migrate from Debian to Ubuntu.
We can make this a priority.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2020-05-06 16:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 0:53 [PATCH] selinux-testsuite: update to work on Debian Stephen Smalley
2020-05-06 13:44 ` Stephen Smalley
2020-05-06 14:57 ` William Roberts
2020-05-06 15:50 ` Stephen Smalley
2020-05-06 15:54 ` William Roberts
2020-05-06 16:37 ` Russell Coker [this message]
2020-05-07 8:35 ` Laurent Bigonville
2020-05-07 12:51 ` Stephen Smalley
2020-05-07 13:13 ` Petr Lautrbach
2020-05-07 13:32 ` Stephen Smalley
2020-05-07 13:41 ` Laurent Bigonville
2020-05-08 3:03 ` Paul Moore
2020-05-13 15:51 ` Stephen Smalley
2020-05-15 16:27 ` William Roberts
2020-05-15 16:41 ` Ondrej Mosnacek
2020-05-15 16:46 ` William Roberts
2020-05-15 17:18 ` Ondrej Mosnacek
2020-05-15 17:24 ` William Roberts
2020-05-07 14:49 ` Russell Coker
2020-05-07 14:54 ` Stephen Smalley
2020-05-07 15:01 ` William Roberts
2020-05-07 15:12 ` Stephen Smalley
2020-05-07 15:22 ` William Roberts
2020-05-12 11:19 ` Petr Lautrbach
[not found] ` <CAJVWAV07O-cQ5EzqYpodjeVRjdtD7ga=bUwEiTm00BaKRMiyFQ@mail.gmail.com>
2020-05-06 19:17 ` Fwd: " Dac Override
2020-05-06 20:07 ` Stephen Smalley
2020-05-06 19:37 ` Ondrej Mosnacek
2020-05-06 19:57 ` Stephen Smalley
2020-05-06 20:26 ` Stephen Smalley
2020-05-07 8:24 ` Ondrej Mosnacek
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=3838641.zh4Wi6GlAV@liv \
--to=russell@coker.com.au \
--cc=bigon@debian.org \
--cc=bill.c.roberts@gmail.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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.