From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] admin_dmesg.patch
Date: Fri, 18 Jun 2010 14:47:03 -0400 [thread overview]
Message-ID: <4C1BBF27.4060606@redhat.com> (raw)
In-Reply-To: <1276777580.2929.192.camel@gorn.columbia.tresys.com>
On 06/17/2010 08:26 AM, Christopher J. PeBenito wrote:
> On Wed, 2010-06-02 at 15:46 -0400, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F14/admin_dmesg.patch
>>
>> Abrt transitions to sosreport_t which transitions to dmesg_t
>>
>> And leaks these descriptors.
>
> It sounds like these should be dontaudit instead (?)
>
No I guess in this case leak is the wrong term. It is passing along an
stdout which points for a file in its /var/run directory
abrt execs "sosreport > /var/run/sosreport/report.dat"
So we want to allow the dmesg output to get stored in this file.
next prev parent reply other threads:[~2010-06-18 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 19:46 [refpolicy] admin_dmesg.patch Daniel J Walsh
2010-06-17 12:26 ` Christopher J. PeBenito
2010-06-18 18:47 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 20:32 Daniel J Walsh
2009-05-21 14:08 Daniel J Walsh
2009-06-11 13:28 ` Christopher J. PeBenito
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C1BBF27.4060606@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.