Hi,
I've just noticed this on setting up my printer for the umpteenth time (its on USB0, but do a reset and I have to manually load ehci, uhci and ohci, usblp and lp in order to get it to work - a pain. I've added into modprobe.conf to loads all of them, but that doesn't seem to work)
The error is this
/usr/sbin/setfiles: invalid context system_u:object_r:printer_device_t on line number 142 /usr/sbin/setfiles: read 432 specifications
Does this really matter and if it does, how do I fix it? /sbin/fixfiles relabel gives the above error.
TTFN
Paul
On Tue, 17 Aug 2004 19:04, Paul paul@all-the-johnsons.co.uk wrote:
I've just noticed this on setting up my printer for the umpteenth time (its on USB0, but do a reset and I have to manually load ehci, uhci and ohci, usblp and lp in order to get it to work - a pain. I've added into modprobe.conf to loads all of them, but that doesn't seem to work)
The error is this
/usr/sbin/setfiles: invalid context system_u:object_r:printer_device_t on line number 142 /usr/sbin/setfiles: read 432 specifications
Is that using strict or targetted policy? What version of the policy?
Hi,
Is that using strict or targetted policy? What version of the policy?
No idea on the type of policy - I don't have anything set on bootup. I have both strict and targetted installed as rpms (1.15.9-1 for both)
TTFN
Paul
Paul wrote:
Hi,
Is that using strict or targetted policy? What version of the policy?
No idea on the type of policy - I don't have anything set on bootup. I have both strict and targetted installed as rpms (1.15.9-1 for both)
TTFN
Paul
/etc/sysconfig/selinux should contain information regarding whether you are set to use strict or targeted policy. Mine was set to strict with permissive mode enabled.
Jim
Hi,
/etc/sysconfig/selinux should contain information regarding whether you are set to use strict or targeted policy. Mine was set to strict with permissive mode enabled.
It's currently set at enforcing and targetted.
Is that correct?
TTFN
Paul
Paul wrote:
Hi,
/etc/sysconfig/selinux should contain information regarding whether you are set to use strict or targeted policy. Mine was set to strict with permissive mode enabled.
It's currently set at enforcing and targetted.
Is that correct?
TTFN
Paul
I believe that is the settings targeted for, which is the aim for FC3.
The strict setting gives a slew of avc errors with selinux-policy-strict-1.15.14-1. I did the fixfiles relabel command before rebooting. The errors during booting seemed to be many. Targetted might be a better setting.
Jim
On Tue, 2004-08-17 at 16:41, Jim Cornette wrote:
The strict setting gives a slew of avc errors with selinux-policy-strict-1.15.14-1. I did the fixfiles relabel command before rebooting. The errors during booting seemed to be many. Targetted might be a better setting.
Please report such denials to fedora-selinux-list, so that the strict policy can be updated if necessary.
Stephen Smalley wrote:
On Tue, 2004-08-17 at 16:41, Jim Cornette wrote:
The strict setting gives a slew of avc errors with selinux-policy-strict-1.15.14-1. I did the fixfiles relabel command before rebooting. The errors during booting seemed to be many. Targetted might be a better setting.
Please report such denials to fedora-selinux-list, so that the strict policy can be updated if necessary.
Thanks! I'll join up and relay the errors to that list.
I was not sure where to post such errors. Bugzilla(One entered, status still new), the test list and did not think to post to the SELinux list.
Jim