From: Russell Coker <russell@coker.com.au>
To: Matej Marusak <mmarusak@redhat.com>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] cockpit web admin system
Date: Tue, 20 Apr 2021 23:31:55 +1000 [thread overview]
Message-ID: <1637645.KEFvsIcdD4@xev> (raw)
In-Reply-To: <CAHLOwD=4oXGPniOO3yR6Gy87-iBN31ETXxeC7k+zykqFrcC7dg@mail.gmail.com>
On Tuesday, 20 April 2021 10:48:32 PM AEST Matej Marusak wrote:
> As a Cockpit developer I would like to mention that Cockpit will ship its
> own policy very soon - it will be the same one that is currently in rawhide
> and it is possible it will involve over time. It will be shipped with
> priority 200 to suppress policy that is shipped by default.
> We first ship it in Fedora-33 and newer as well as rhel-9 and newer. We
> have a plan to ship it in Debian as well. Other OSes may come later.
>
> This is being developed in [1].
>
> MM
>
> [1] https://github.com/cockpit-project/cockpit/pull/15707
The same policy won't work for Red Hat and for Refpolicy systems (including
Debian). Many interfaces have different names and some interfaces do
different things.
You will have to ship 2 policies if you want to support Red Hat and the rest.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2021-04-20 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 9:36 [PATCH] cockpit web admin system Russell Coker
[not found] ` <CAHLOwD=4oXGPniOO3yR6Gy87-iBN31ETXxeC7k+zykqFrcC7dg@mail.gmail.com>
2021-04-20 13:31 ` Russell Coker [this message]
2021-04-20 13:49 ` Dominick Grift
2021-04-26 12:47 ` Chris PeBenito
2021-04-26 13:22 ` Dominick Grift
2021-04-26 13:34 ` Dominick Grift
2021-04-26 14:21 ` Dominick Grift
2021-04-26 14:31 ` Dominick Grift
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=1637645.KEFvsIcdD4@xev \
--to=russell@coker.com.au \
--cc=mmarusak@redhat.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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.