Red Hat Bugzilla – Bug 853954
Warning about conflicting contexts for /usr/lib64/libzip/include/zipconf.h versus /usr/include/zipconf-64.h
Last modified: 2012-09-17 19:13:57 EDT
I just remembered that yesterday after doing "fixfiles onboot; reboot" I got a warning during the relabel about conflicting file contexts in the policy for: /usr/lib64/libzip/include/zipconf.h versus /usr/include/zipconf-64.h
These files appear to be hardlinks from each other:
[hans@shalem qemu]$ ls -l /usr/lib64/libzip/include/zipconf.h
-rw-r--r--. 2 root root 994 Jul 20 20:24 /usr/lib64/libzip/include/zipconf.h
[hans@shalem qemu]$ ls -l /usr/include/zipconf-64.h
-rw-r--r--. 2 root root 994 Jul 20 20:24 /usr/include/zipconf-64.h
So this may be considered a libzip packaging bug, if so, please describe what needs to be changed from an selinux policy pov and change the component.
Well this a problem with hardlinks. We need to add labeling for both paths. Is hardlink needed?
I can use symlink instead of hardlink if that's a problem
(In reply to comment #2)
> I can use symlink instead of hardlink if that's a problem
If that is possible using a symlink would be a good solution to silenc the warning selinux onboot relabeling gives about these 2 files.
libzip-0.10.1-4.fc18 has been submitted as an update for Fedora 18.
libzip-0.10.1-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.