On Mon, Mar 7, 2022 at 8:34 AM Simo Sorce <simo(a)redhat.com> wrote:
If this is just for debugging from time to time I think you could
simply log in the same directories where gssproxy has permission to
create ccache files under /var/lib, that would not require any changes
to the selinux policy afaik.
Sure it is not a log directory, but then, this is not intended for
regular logging either...
Simo.
Makes sense.
While creating the SELinux module is trivial, there could be a
non-trivial amount of steps that would have to be taken to load the
module for users with compliance requirements.
Thanks!
--
Simo Sorce
RHEL Crypto Team
Red Hat, Inc
_______________________________________________
gss-proxy mailing list -- gss-proxy(a)lists.fedorahosted.org
To unsubscribe send an email to gss-proxy-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/gss-proxy@lists.fedorahosted...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Jacob Shivers