|Summary:||[Feature request] Automatic submission of SELinux AVC denials|
|Product:||[Fedora] Fedora||Reporter:||Viktor Erdelyi <verdelyi>|
|Component:||setroubleshoot||Assignee:||Daniel Walsh <dwalsh>|
|Status:||CLOSED NEXTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-01-21 21:21:12 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Viktor Erdelyi 2008-05-19 22:02:42 UTC
It would be great if there was an option to have Fedora automatically submit SELinux conflicts to some central server (the ones that pop up in a bubble), and the Fedora team could select the most common reports and fix them without having to wait for bugzilla entries. Just an idea...
Comment 1 Viktor Erdelyi 2008-05-19 22:04:34 UTC
(I actually don't know what those reports are trying to tell me but would be willing to click on a magic "Send to developers" button :) )
Comment 2 Daniel Walsh 2008-05-20 00:26:03 UTC
I agree, the problem is on the server side. We need some infrastructure to handle them and prevent spamming. Consolodation so we can map similar avc's to the same problem.
Comment 3 Viktor Erdelyi 2009-03-21 12:14:50 UTC
Just an idea: is it possible to use the same technique that kerneloops uses?
Comment 4 Daniel Walsh 2009-03-23 17:33:02 UTC
That would be the idea or come to a common fedora infrastructure where bugzillas could be reported an triaged.
Comment 5 Bug Zapper 2009-06-09 09:34:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Daniel Walsh 2010-01-21 21:21:12 UTC
Fixed in Fedora 12.