Bug 2019962
Summary: | "seinfo --constrain" doesn't produce identical output when constraints haven't changed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Stodola <jstodola> |
Component: | setools | Assignee: | Petr Lautrbach <plautrba> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9.0 | CC: | lvrabec, mmalik, plautrba, qe-baseos-security, vmojzis |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | setools-4.4.0-4.el9 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | 2019961 | Environment: | |
Last Closed: | 2022-05-17 15:58:06 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: |
Description
Jan Stodola
2021-11-03 17:37:22 UTC
It looks like permissions are not sorted in the seinfo output:
# seinfo --constrain | sort > 1.txt
# seinfo --constrain | sort > 2.txt
# diff 1.txt 2.txt | grep alg_socket
< constrain alg_socket { relabelto create relabelfrom } (u1 == u2 or ( t1 == can_change_object_identity ));
> constrain alg_socket { relabelfrom create relabelto } (u1 == u2 or ( t1 == can_change_object_identity ));
#
https://github.com/SELinuxProject/setools/pull/66 is accepted and merged upstream. https://gitlab.com/redhat/centos-stream/rpms/setools/-/commit/0e7e0ffd80f8425438701c6a1f51a6b938a5978e https://gitlab.com/redhat/centos-stream/rpms/setools/-/commit/439a9c0061bfd627430932993cc21c6ca1ca8750 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 (new packages: setools), 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-2022:3982 |