On Fri, 2016-12-09 at 06:51 +0800, Ed Greshko wrote: > > On 12/09/16 06:37, Patrick O'Callaghan wrote: > > On Fri, 2016-12-09 at 05:57 +0800, Ed Greshko wrote: > > > On 12/08/16 18:44, Patrick O'Callaghan wrote: > > > > Got the above after updating to kernel 4.8.11-300.fc25.x86_64. I > > > > noticed it when my NFS mounts failed. Nothing else has changed. > > > > > > > > Any ideas? > > > > > > > > > > This may be your issue? > > > > > > Just seen on the selinux list.... > > > > > > The latest version of the rpcbind package (0.2.4-0) has moved the rpcbind > > > executable from > > > /sbin/rpcbind to /usr/bin/rpcbind. The selinux-policy (3.13.1-224) > > > doesn't yet reflect > > > this change, so the rpcbind executable ends up labeled bin_t instead of > > > rpcbind_exec_t. > > > > OK, looks promising. I guess this will probably fix itself with the next > > update. > > > > Thanks. > > You could, of course, verify this is your issue by running in permissive mode.
Yes, I did that already. It worked. > Or you could change the context on the file by following the instructions > here. > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html OK poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
