Bug 244755
Summary: | Selinux issuing alerts, user has no clue what to do | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Williams <jwilliams> |
Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | dwalsh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-04 20:11:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Williams
2007-06-18 23:58:07 UTC
The goal of this application is to inform the user that something has happened on the system that SELinux has denied. The explanation tries to explain what happened and possible actions. In this case the system was not able to find a good diagnosis so it throws the catch all. From examining the alert, it looks like you have some kind of installation program that is running a shell program. What rpm type program are you running? You also have something that is labeled unlabeled_t which indicates you have a file system that SELinux does not understand. As far as telling the user whether there is an intrusion or not, the tools are currently good enough to diagnose at that level. From this sealert, almost guaranteed this is a configuration/bug in SELinux and not an intrusion. |