From: Russell Coker <russell@coker.com.au>
To: Laurent Bigonville <bigon@debian.org>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
William Roberts <bill.c.roberts@gmail.com>,
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: Fri, 08 May 2020 00:49:23 +1000 [thread overview]
Message-ID: <1916523.qzzCliNl98@liv> (raw)
In-Reply-To: <cf747e50-ca5b-429f-1af2-afaa16ee29be@debian.org>
On Thursday, 7 May 2020 6:35:11 PM AEST Laurent Bigonville wrote:
> If people are using preseed installations (kickstart equivalent), I
> think that enabling SELinux in the installer shouldn't be too difficult
> (installing the needed packages, modifying the files and relabeling with
> fixfiles). It's obviously not user friendly, but the question is what's
> the target here.
If we want to do that properly then I guess we want SE Linux enabled in the
kernel that the installer uses and then have the policy installed early in the
installation so the files can have the correct labels from the start instead of
having a relabel process afterwards.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2020-05-07 14:49 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
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 [this message]
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=1916523.qzzCliNl98@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.