On 09/01/2015 05:10 AM, Chris Murphy wrote: > After a clean install of F23 server from netinstall media, running > restorecon I get a pile of changed files. Why aren't they correct to > begin with? > > Examples: > > > restorecon reset > /usr/lib/modules/4.2.0-0.rc8.git0.1.fc23.i686/modules.symbols context > system_u:object_r:modules_object_t:s0->system_u:object_r:modules_dep_t:s0 > > restorecon reset /boot/System.map-4.2.0-0.rc8.git0.1.fc23.i686 context > system_u:object_r:modules_object_t:s0->system_u:object_r:system_map_t:s0 > > restorecon reset /boot/vmlinuz-4.2.0-0.rc8.git0.1.fc23.i686 context > system_u:object_r:modules_object_t:s0->system_u:object_r:boot_t:s0 > > restorecon reset /var/lib/os-prober/labels context > unconfined_u:object_r:user_tmp_t:s0->unconfined_u:object_r:bootloader_var_lib_t:s0 > > restorecon reset /var/log/dnf.log context > system_u:object_r:rpm_log_t:s0->system_u:object_r:var_log_t:s0 > > restorecon reset > /var/cache/dnf/updates-testing-200adbd074da487f/repodata/repomd.xml > context system_u:object_r:rpm_tmp_t:s0->system_u:object_r:rpm_var_cache_t:s0 > > > So I asked about it on the test@ list and AdamW says it's the same > with Fedora 22, so it's not a new thing. > > Is this a bug with the originated package setting the label wrongly? > Does it make sense to RFE anaconda to run restorecon as part of > post-install scripts? > > Could you please open a new bug against Fedora? We will investigate it if we can place a fix in selinux-policy pkgs or if it requires another fix. Thank you. -- Miroslav Grepl Senior Software Engineer, SELinux Solutions Red Hat, Inc. -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux
