From: Petr Lautrbach <lautrbach@redhat.com>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: selinux@vger.kernel.org
Subject: Re: Adding SElinux support for a service
Date: Fri, 21 Nov 2025 11:25:44 +0100 [thread overview]
Message-ID: <87ecprfzrr.fsf@redhat.com> (raw)
In-Reply-To: <60A8D560-3A88-48B7-88AE-1D7023AF2B44@redfish-solutions.com>
Philip Prindeville <philipp_subx@redfish-solutions.com> writes:
>> On Nov 20, 2025, at 2:15 PM, Stephen Smalley <stephen.smalley.work@gmail.com> wrote:
>>
>> On Thu, Nov 20, 2025 at 3:14 PM Philip Prindeville
>> <philipp_subx@redfish-solutions.com> wrote:
>>>
>>> Hi,
>>>
>>> I'm working on SElinux support for a server that talks to a PCIe GPS card.
>>>
>>> Is there a guide to how to port a new service to SElinux, for instance how to give it its own context? Or, in the absence of a guide, what GitHub project can I look at for the supporting commits that were done to achieve the same?
>>
>> Can you elaborate a little on what it is you want to do? Do you have
>> SELinux enabled and enforcing already on the base system and just want
>> to add policy for a new service to confine it and/or control what
>> other processes can talk to it?
>> Or do you also want the service to be SELinux-aware, aka a userspace
>> object manager, where it enforces its own security policy over its own
>> objects and operations?
>> What's your starting point?
>
>
> Yes, I have an SElinux system (RHEL 10.0) and I’m running the daemon on it. I want to package policy rules with the daemon, but yes, I also want to confine the daemon to its own context.
>
> Currently only chronyd or ntpd would talk to it, either by the char device it creates, or else the shared memory segment it creates.
Take a look at https://fedoraproject.org/wiki/SELinux/IndependentPolicy
Also given that this is for rpm based distro using fedora-selinux
policy, selinux@lists.fedoraproject.org might the better place to get a
help.
Petr
prev parent reply other threads:[~2025-11-21 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 20:03 Adding SElinux support for a service Philip Prindeville
2025-11-20 21:15 ` Stephen Smalley
2025-11-21 2:48 ` Philip Prindeville
2025-11-21 10:25 ` Petr Lautrbach [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=87ecprfzrr.fsf@redhat.com \
--to=lautrbach@redhat.com \
--cc=philipp_subx@redfish-solutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox