Bug 799676
Summary: | SELinux is preventing /usr/bin/dia from 'mmap_zero' accesses on the memprotect Unknown. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | nomnex <nomnex> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | dominick.grift, dwalsh, mgrepl, nomnex |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:14e7302ff3c4142d1d5aac78367d804c9fb24f65b7ee4c28f79de6f05e4f5322 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-05 09:24:46 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
nomnex
2012-03-04 07:08:31 UTC
setroubleshoot tells you what to do. "mmap_zero" is pretty dangerous access which we do not want to allow by default. Does "dia" work correctly? Unfortunately Dia kept crashing after each new SELinux warning msg. I have follow the direction of the SELinux troubleshooting (well done, BTH), and I passed the command to allow "mmap_zero", although I don't know what I am doing. Am I the only Dia user on F15 affected by this warning? My understanding of SELinux is too vague (that's the police officer, with a stick, inside my box?) Nevertheless, why does Dia from the Fedora repository requests a custom rule, potentially dangerous? |