From: "José Pekkarinen" <jose.pekkarinen@unikie.com>
To: "Weber, Matthew L Collins" <Matthew.Weber@collins.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Adam Duskett <aduskett@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] Re: [PATCH v2] package/libselinux: Add autorelabel for first boot
Date: Fri, 3 Sep 2021 09:53:50 +0300 [thread overview]
Message-ID: <CAJPV9Mrsi9+JKT+c5tRAD8OzAMB2TQhCD5PweeWLb0jn4pHm=w@mail.gmail.com> (raw)
In-Reply-To: <CAJPV9MqR1ERA5dLyj6uKDHQ5GXGG5BH7bN6g98-eFXq+mK-5qw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]
On Wed, Aug 25, 2021 at 2:33 PM José Pekkarinen <jose.pekkarinen@unikie.com>
wrote:
>
>
> On Mon, Aug 23, 2021 at 5:19 PM Weber, Matthew L Collins <
> Matthew.Weber@collins.com> wrote:
>
>>
>>
> Hi,
>
> I'm afraid the init script may not work since it
>
> references paths only existing in Centos, not in buildroot
> userspace(specifically, /usr/share/selinux/ and
> /selinux/enforce). However, we could use it to add the
> missing pieces of autorelabel for the restorecond init script
> or fix it and submit it. I'm happy to go for it, I'd like to hear
> what the upstream point of view is.
>
Hi,
Can I have some comments from maintainers whether
autorelabeling can be enabled in buildroot or not, and what
would be the preferred way? It seems to me that I can propose
a new init script for policycoreutils package that check for the
autorelabel file and trigger the missing commands. Would
that be a good idea?
Best regards.
José.
[-- Attachment #1.2: Type: text/html, Size: 2429 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-09-03 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 9:29 [Buildroot] [PATCH v2] package/libselinux: Add autorelabel for first boot José Pekkarinen
2021-08-19 21:05 ` Yann E. MORIN
2021-08-20 12:19 ` José Pekkarinen
2021-08-20 19:15 ` Yann E. MORIN
2021-08-20 19:16 ` Yann E. MORIN
2021-08-23 5:43 ` José Pekkarinen
2021-08-23 14:19 ` [Buildroot] [External] " Weber, Matthew L Collins via buildroot
2021-08-25 11:33 ` José Pekkarinen
2021-09-03 6:53 ` José Pekkarinen [this message]
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='CAJPV9Mrsi9+JKT+c5tRAD8OzAMB2TQhCD5PweeWLb0jn4pHm=w@mail.gmail.com' \
--to=jose.pekkarinen@unikie.com \
--cc=Matthew.Weber@collins.com \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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.