Re: [RFC 2] logging.te: systemd-journald: loose ends

On 8/9/26 7:35 AM, Dominick Grift wrote:
> Russell Coker <[email protected]> writes:
>
>> On Sunday, 9 August 2026 21:05:27 AEST Dominick Grift wrote:
>>> Do you have any type transition rules for those at all?
>>>
>>> sesearch -T -s syslogd_t -t syslogd_runtime_t -c sock_file
>> # sesearch -T -s syslogd_t -t syslogd_runtime_t -c sock_file
>> type_transition syslogd_t syslogd_runtime_t:sock_file devlog_t
>> io.systemd.journal;
>>
>> No I only have one rule.
> Thanks. I think the user may not have these sockets activated and that
> therefore they get created by systemd-journald instead in his
> scenario. systemd-journald itself does not seems to use
> get/setfscreatecon as it needs a type transition for io.systemd.journal
> too.
>
> I suppose the question becomes whether refpolicy wants to support the
> scenario where the syslog socket unit is not enabled.

Yes, this should be corrected.


-- 
Chris PeBenito