Open luckylittle opened 1 year ago
Is there anything I can actually do to help? This looks like a downstream issue - I do not maintain the RHEL package.
I'm not sure actually. I think the package sepolicy
needs to include this rule.
This may be a security bug. I found this issue while researching it for another project. Adding a specific SELinux policy is just a last resort workaround. Fixing the linking during the build is best. Posting this here hoping it can help:
https://akkadia.org/drepper/selinux-mem.html (see execmod) https://akkadia.org/drepper/textrelocs.html (more details about the text relocation problem).
This is an issue probably only on RHEL9.
Describe the bug CopyQ cannot start and gets terminated. These messages related to SELinux appear in the
/var/log/messages
:To Reproduce Steps to reproduce the behavior:
6.3.2
on RHEL9copyq
Expected behavior CopyQ expected to start without generating a local SELinux policy module
Screenshots N/A
Version, OS and Environment (Get details from
copyq version
command if possible.)9.0
(Plow),5.14.0-70.26.1.el9_0.x86_64
Additional context The temporary fix was:
sudo ausearch -c 'copyq' --raw | audit2allow -M my-copyq
sudo semodule -i my-copyq.pp