Bug 1664983
Summary: | SELinux prevents kadmind from searching in /var/lib/softhsm directory | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Kaleem <ksiddiqu> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | abokovoy, lslebodn, lvrabec, mmalik, ndehadra, nmavrogi, plautrba, ssekidde, zpytela |
Target Milestone: | rc | Keywords: | AutoVerified |
Target Release: | 8.1 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.14.3-6.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 22:09:45 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: | |||
Bug Depends On: | 1673107, 1682526 | ||
Bug Blocks: |
Description
Kaleem
2019-01-10 08:16:11 UTC
*** Bug 1689921 has been marked as a duplicate of this bug. *** This is due to p11-kit pulling in softhsm2 module into any application that initializes openssl engines. Kaleem, could you please try this workaround: ---------------------------------------- # cat /etc/pkcs11/modules/softhsm2.module module: /usr/lib64/pkcs11/libsofthsm2.so disable-in: kadmind ---------------------------------------- Nikos, this is another case of p11-kit creating issues with SELinux contexts. There is no way so far to contain pkcs11 accesses. May be we need to integrate p11-kit with SELinux so that module loads are done in a context that can be granted certain access rights? Please try workaround of https://bugzilla.redhat.com/show_bug.cgi?id=1664983#c3 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, 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-2019:3547 |