Hide Forgot
Description of problem: 1. Proposed title of this feature request [RFE] add possibility to check sum of loaded module 2. Who is the customer behind the request? Account: RED HAT IT/IS 5243891 TAM customer: yes CSM customer: yes Strategic: yes 3. What is the nature and description of the request? Use case: Ansible loads a module. If I then need to make changes to this policy in the future, how can Ansible compare the .pp file in config management with the state loaded on the system? Need some mechanism to compare loaded module with definition of the module we expect to be running. 4. Why does the customer need this? (List the business requirements here) Having Ansible reload the module every run will cause problems in real operations. 5. How would the customer like to achieve this? (List the functional requirements here) Introduce st like `semodule -l --checksum` that could be compared with the module definition. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? 9. Is the sales team involved in this request and do they have any additional input? 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? Yes
https://lore.kernel.org/selinux/20211116132711.163668-1-plautrba@redhat.com/T/#u
https://github.com/SELinuxProject/selinux/commit/ed4813be615182b0f4b8fcabbaad0256ed80845d https://github.com/SELinuxProject/selinux/commit/f37b3e94d328bcb36d57e571e755922a4237bdc7 https://github.com/SELinuxProject/selinux/commit/c28763c4c9736fd6d83a11740f97035d076a1d71
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 (policycoreutils 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-2022:2068