Refactor the custom exec context setting code to look like setexecfilecon() in case the real one is not available to eliminate pesky behavioral differences between the two cases.
This fixes a concrete bug of libselinux setexecfilecon() returning with an error when security_getenforce() returns with -1 (such as a bare chroot with no /sys mounts etc), causing us to spit out useless error messages in that case ever since fixing the bogus if-logic in commit ab601b882b9d9d8248250111317615db1aa7b7c6. Fixes: #1077 You can view, comment on, or merge this pull request online at: https://github.com/rpm-software-management/rpm/pull/1079 -- Commit Summary -- * Use common error logic regardless of setexecfilecon() availability -- File Changes -- M plugins/selinux.c (46) -- Patch Links -- https://github.com/rpm-software-management/rpm/pull/1079.patch https://github.com/rpm-software-management/rpm/pull/1079.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/1079
_______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
