Bug 2203359
Summary: | SELinux AVC from rhsm-service | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Marko Myllynen <myllynen> |
Component: | selinux-policy | Assignee: | Nobody <nobody> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.2 | CC: | lvrabec, mmalik, ptoscano, zpytela |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-38.1.13-1.el9 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-07 08:52:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Deadline: | 2023-05-16 |
Description
Marko Myllynen
2023-05-12 07:09:22 UTC
Hm I guess the new kTLS module gets loaded automatically... and now every application that does TLS connections via lower-level libraries (CPython) needs their own SELinux rules? A bit of sigh... (Side note: in case it applies, please fix this for Fedora as well, thanks!) (In reply to Pino Toscano from comment #1) > Hm I guess the new kTLS module gets loaded automatically... and now every > application that does TLS connections via lower-level libraries (CPython) > needs their own SELinux rules? A bit of sigh... I see it as a kind of a contest who is the first one, may be that's why the service does not fail eventually. > > (Side note: in case it applies, please fix this for Fedora as well, thanks!) We almost always make changes in Fedora first. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:6617 |