Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAHC9VhRAXQyzG7OsgXQfWT09qEFQRmeN2foGLGnU8cHdRKePUA@mail.gmail.com>
 <87r0qcotc0.fsf@redhat.com> <CAJ2a_Dd0EM10WsgrEGY_SUh3L444d23_T1F36pphdJDnk_DSLg@mail.gmail.com>
In-Reply-To: <CAJ2a_Dd0EM10WsgrEGY_SUh3L444d23_T1F36pphdJDnk_DSLg@mail.gmail.com>
From:   Paul Moore <paul@paul-moore.com>
Date:   Mon, 19 Jun 2023 17:58:07 -0400
Message-ID: <CAHC9VhRbEa8keNU=oNd1oNCkZuYYUZdLhvJTqhJ522sB9Fo=sg@mail.gmail.com>
Subject: Re: SELinux and systemd integration
To:     =?UTF-8?Q?Christian_G=C3=B6ttsche?= <cgzones@googlemail.com>
Cc:     Petr Lautrbach <plautrba@redhat.com>, selinux@vger.kernel.org,
        selinux-refpolicy@vger.kernel.org,
        Lennart Poettering <lennart@poettering.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, Jun 17, 2023 at 2:09=E2=80=AFPM Christian G=C3=B6ttsche
<cgzones@googlemail.com> wrote:
> On Fri, 16 Jun 2023 at 07:43, Petr Lautrbach <plautrba@redhat.com> wrote:
> > Paul Moore <paul@paul-moore.com> writes:
> >
> > > Hello all,
> > >
> > > Amongst Christian's various other SELinux contributions, over the pas=
t
> > > several years Christian has been working on improving the SELinux
> > > integration in systemd.  One of the things that Christian has been
> > > working on is revamping the SELinux permissions that systemd uses for
> > > unitfile operations, both to resolve problems and generally improve
> > > the mapping of permissions to systemd operations.  As this work has
> > > been languishing for several years, I would like to see if we can get
> > > things "unstuck" by proposing two things:
> > >
> > > 1. I've provided links to the systemd GH PRs below, but I think it
> > > might be helpful if Christian could provide a quick summary of the ne=
w
> > > permissions, how they map to systemd operations, and how they map to
> > > the existing SELinux/systemd permissions with a focus on helping
> > > policy developers migrate existing SELinux policies.
> > >
> > > 2. Given the significance of systemd to modern Linux distributions, I
> > > think it might be a good idea if we selected a SELinux "liaison" for
> > > the systemd project.  This person, or group of people, would work wit=
h
> > > the systemd folks to keep the SELinux integration in good working
> > > order, review systemd code as necessary, and help represent the
> > > SELinux project within systemd.
> > >
> > > How does that sound to everyone?  If we are in agreement on #2, and
> > > assuming he would be willing to help out, I would like to nominate
> > > Christian as our SELinux liaison to systemd; any objections?  Anyone
> > > else interested in helping out?
> >
> > I agree with the Christian's nomination.
> >
> > As for #1, I looked on both, but I have to admit that I had a lack of
> > understanding of the problem and so I would need some time to get
> > into it. Therefore I postponed it due to other priorities, (but never
> > come back). If it's still open I'll focus on it next week.
> >
> >
> > > For reference, Christian's systemd PRs on GH:
> > > * https://github.com/systemd/systemd/pull/10023
> > > * https://github.com/systemd/systemd/pull/20387
> > >
> >
> > Thanks,
> >
> > Petr
> >
>
> Hi all,
>
> Thanks Paul for attracting some attention to the SELinux integration
> of systemd.  It has been several months since I last worked on the
> systemd related patches, so they all need a rebase and another round
> of testing.
>
> Addressing the first point, here are some details about the changes I
> would like to see in systemd ...

Thanks for all the details Christian :)

--=20
paul-moore.com