Bug 235145
Summary: | fuse changes security context of /etc/mtab | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Yves Perrenoud <yves-redhat> |
Component: | fuse | Assignee: | Peter Lemenkov <lemenkov> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | extras-qa |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-05 21:26:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yves Perrenoud
2007-04-03 23:11:55 UTC
Hmmm. Could you check whether it works if we BR only libselinux-devel? Or its necessary to BR both libselinux and libselinux-devel? What triggers the inclusion of the selinux code in fusermount is based on the results of an AC_CHECK_LIB (for libselinux) I added to configure.in. The way configure checks for the presents of the library is by compiling a snippet of test code using a "-l<lib>". Hence gcc must be only looking for libselinux.a as there's no attempt to actually execute the code. Thus I'm fairly confident that only including "libselinux-devel" in the BuildRequires should do the job. OK, added. Let's wait next version. |