Description of problem: SELinux context differs when I run rpm -V for the current RHEL4 build of sysklogd-1.4.1-27.el4 and the previous version sysklogd-1.4.1-26_EL, even if freshly installed. sysklogd-1.4.1-44.el5.i386, the current release for RHEL5 doesn't have the same problem. %> rpm -q sysklogd sysklogd-1.4.1-27.el4.x86_64 %> rpm -V sysklogd S.5....T. c /etc/sysconfig/syslog S.5....TC c /etc/syslog.conf ^ # verify error 'C' = SELinux Context Differs I have a feeling this isn't a major problem, considering the older version had the same problem...but nonetheless, less verify errors, the better. I'm honestly not sure what's causing the verify error to occur, perhaps it's a bug in rpm -V itself, because when I check the context of syslog.conf, it appears to be correct. %> rpm -V sysklogd S.5....TC c /etc/syslog.conf ^ %> ls -Z /etc/syslog.conf -rw-r--r-- root root user_u:object_r:etc_t /etc/syslog.conf %> restorecon /etc/syslog.conf %> ls -Z /etc/syslog.conf -rw-r--r-- root root user_u:object_r:etc_t /etc/syslog.conf %> rpm -V sysklogd S.5....TC c /etc/syslog.conf ^ %> rpm -q sysklogd sysklogd-1.4.1-27.el4.x86_64 Version-Release number of selected component (if applicable): sysklogd-1.4.1-27.el4 How reproducible: always Steps to Reproduce: 1.see above 2. 3. Expected results: no SELinux context verify error
It is checking the SELinux user of the file user_u versus system_u. If you run restorecon -F /etc/syslog.conf it should fix the file so RPM will not complain. This was fixed to not check the user componant in later versions of rpm.
so, is this rpm problem? Should I reassign the issue?
Exactly what I'm thinking, should this bug be reassigned to rpm then? Should rpm be checking the user of the file user_u versus system_u?
I think the problem is the checking at all. rpm -V checking of SELinux context was removed from newer versions or rpm. It is arguable either way, that this is correct behavior, since it does not match the default context.