# restorecon -rvn /dev
restorecon reset /dev/pts/ptmx context system_u:object_r:devpts_t:s0->system_u:object_r:ptmx_t:s0
I would expect the file to be labeled correctly in the first place.
this has _not_ been fixed by
Yes we know, we are not sure what is causing it but it does not seem to cause any problems.
I am not even sure what the difference between the two files is.
ls -lZ /dev/ptmx /dev/pts/ptmx
crw-rw-rw-. root tty system_u:object_r:ptmx_t:s0 /dev/ptmx
c---------. root root system_u:object_r:devpts_t:s0 /dev/pts/ptmx
Maybe we should just change the label of /dev/pts/ptmx to devpts_t and forget about it. It does not look like this device path is used.
$0.05 of observations and opinions:
crw-rw-rw-. 1 root tty 5, 2 Sep 21 11:04 /dev/ptmx
c---------. 1 root root 5, 2 Sep 21 10:44 /dev/pts/ptmx
- so it is the same device but /dev/ptmx can actually be used and follows the local OS policy for unix access control. I guess devpts is for "internal" low-level use only, so it could make sense that they have different labels.
Ok I am just going to remove the label so that the tools will not complain, and see if it ends up causing any problems, which it has not so far.
Fixed in selinux-policy-3.10.0-33.fc16
selinux-policy-3.10.0-36.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-36.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
selinux-policy-3.10.0-38.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.