[ale] SELinux & abrtd
Jim Kinney
jim.kinney at gmail.com
Fri Sep 17 14:15:21 EDT 2010
The popup notice has a "show extended/view details" feature. Included in
that is a command line instruction to run to allow the blocked access. There
are typically 2 ways to resolve these: temporary and permanently. Do the
temp version AND hit the bug notice button to send the problem upstream.
yeah, I know, the bug notice process is what croaked in the first place.
Usual abrtd stuff I've seen involve temp files (ditto on yum selinux issues)
so allowing the read/write is OK.
On Fri, Sep 17, 2010 at 11:52 AM, Drifter <drifter at oppositelock.org> wrote:
> got this message this morning:
>
> SELinux denied access requested by abrtd. It is not expected that this
> access is required by abrtd and this access may signal an intrusion attempt.
> It is also possible that the specific version or configuration of the
> application is causing it to require additional access.
>
> All I know about abrtd is what Google turned up:
>
> abrt is a tool to help users to detect defects in applications and
>
> to create a bug report with all informations needed by maintainer to fix it.
>
> It uses plugin system to extend its functionality.
>
> So I think my question is
>
> How do I get SELinux to let the program do its thing?
>
> Or should I just not give a damn?
>
> Sean
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
--
--
James P. Kinney III
I would rather stumble along in freedom than walk effortlessly in chains.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20100917/d371ae1f/attachment.html
More information about the Ale
mailing list