On Tue, 21 Mar 2023 21:50:22 +0100
Patrick Dupre wrote:
> >
> > >> I get the following SELinux security alert which seems to be
> > >> difficult to fix because of the number of things to do.
> >
> > I don't understand why you think two things to do is difficult.
>
> Because, every time th
>
> >> I get the following SELinux security alert which seems to be
> >> difficult to fix because of the number of things to do.
>
> I don't understand why you think two things to do is difficult.
Because, every time that I make
semanage fcontext -a -t syslog_conf_t '/var/usermin/miniserv.pid'
s
I get the following SELinux security alert which seems to be
difficult to fix because of the number of things to do.
I don't understand why you think two things to do is difficult.
You can generate a local policy module to allow this access.
Do allow this access for now by executing:
# ausearc
Hi
On Mon, 20 Mar 2023 10:28:35 +0100 Patrick Dupre wrote:
> I did not get retuen about my request.
There was. Please, see the archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/NEDFHZEENU3YPWXCKENB2FDYL4YHYOW6/#5LDTZCEMCGHQHKSLJXRS3QIFVZ3IYE73
--
fr
Hello,
I did not get retuen about my request.
This alert is annoying because it pop up all the time,
and because it prevents the screen lock.
Is there any thing that I can make?
Thank.
===
Patrick DUPRÉ
Hi.
On Thu, 16 Mar 2023 10:32:27 +0100 Patrick Dupre wrote:
> SELinux is preventing systemd from open access on the file
> /var/usermin/miniserv.pid.
Another solution beside fixing the selinux context would perhaps be to change
the associated .service file to not use a .pid file.
What is the
On Thu, 16 Mar 2023 10:32:27 +0100
Patrick Dupre wrote:
> I get the following SELinux security alert which seems to be difficult
> to fix because of the number of things to do.
There is really only one thing to do, just run the two commands with
the proper selinux context selected as filetype.
