psidfiles_init errors
Everyone,
Could someone please explain the following errors?
psidfiles_init: invalid context system_u:object_r:dmesg_exec_t (psid 89). psidfiles_init: invalid context system_u:object_r:xdm_log_t (psid 92). psidfiles_init: invalid context system_u:object_r:minilogd_exec_t (psid 120). ... psidfiles_init: invalid context system_u:object_r:writeable_t (psid 37). psidfiles_init: invalid context system_u:object_r:mesg_exec_t (psid 47). psidfiles_init: invalid context Brad:object_r:writeable_t (psid 62). psidfiles_init: invalid context system_u:object_r:samba_t (psid 64).
Thanks,
Brad
__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 10 lines · Brad Chapman
Could someone please explain the following errors?
psidfiles_init: invalid context system_u:object_r:dmesg_exec_t (psid 89). psidfiles_init: invalid context system_u:object_r:xdm_log_t (psid 92). psidfiles_init: invalid context system_u:object_r:minilogd_exec_t (psid 120). ... psidfiles_init: invalid context system_u:object_r:writeable_t (psid 37). psidfiles_init: invalid context system_u:object_r:mesg_exec_t (psid 47). psidfiles_init: invalid context Brad:object_r:writeable_t (psid 62). psidfiles_init: invalid context system_u:object_r:samba_t (psid 64).
These are file types that existed in old versions of the policy but which don't exist any more. They still have entries in the ...security database because there's no code to clean them up (IMHO they should be removed when there are no files of that context on the file system any more).
To avoid the messages add the following to your policy:
type dummy_file_t alias { dmesg_exec_t xdm_log_t minilogd_exec_t ... };
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 7 lines · Russell Coker
These are file types that existed in old versions of the policy but which don't exist any more. They still have entries in the ...security database because there's no code to clean them up (IMHO they should be removed when there are no files of that context on the file system any more).
To avoid the messages add the following to your policy:
typedummy_file_talias {dmesg_exec_txdm_log_tminilogd_exec_t... };
You can run 'make reset' in your policy directory and then reboot to eliminate dead entries from the persistent label mapping. With regard to automatically removing such entries, it isn't clear that it would be desirable and it would require maintaining persistent reference counts on the PSIDs within each filesystem. As to why it might not be desirable, consider the following:
1) Transient files (e.g. temporary files) with derived types may be frequently created and destroyed. Adding the overhead of re-creating the PSID/context entry for each such create/destroy cycle would be undesirable.
2) File deletion doesn't truly destroy the data. It may be desirable to be able to check the set of contexts that have _ever_ been used for files within a filesystem to determine whether the disk needs to be scrubbed.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 7 lines · Stephen Smalley
Quoted 6 lines · Russell Coker
These are file types that existed in old versions of the policy but which don't exist any more. They still have entries in the ...security database because there's no code to clean them up (IMHO they should be removed when there are no files of that context on the file system any more).
Quoted 5 lines
Quoted 2 lines
To avoid the messages add the following to your policy:
typedummy_file_talias {dmesg_exec_txdm_log_tminilogd_exec_t... };You can run 'make reset' in your policy directory and then reboot to eliminate dead entries from the persistent label mapping.
That option is too nasty to consider.
Quoted 6 lines
With regard to
automatically removing such entries, it isn't clear that it would be desirable and it would require maintaining persistent reference counts on the PSIDs within each filesystem. As to why it might not be desirable, consider the following:
Quoted 8 lines
1) Transient files (e.g. temporary files) with derived types may be frequently created and destroyed. Adding the overhead of re-creating the PSID/context entry for each such create/destroy cycle would be undesirable.
2) File deletion doesn't truly destroy the data. It may be desirable to be able to check the set of contexts that have _ever_ been used for files within a filesystem to determine whether the disk needs to be scrubbed.
In that case why not just remove the error message on boot? If this is the desired functionality then surely our log files don't need to get filled because of it.
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 3 lines · Russell Coker
In that case why not just remove the error message on boot? If this is the desired functionality then surely our log files don't need to get filled because of it.
I suppose we could disable printing of these messages by default. Historical note: The messages used to only occur once, and then the entries would be purged, but that had to change to support the initrd functionality that you wanted.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.