All of lore.kernel.org
 help / color / mirror / Atom feed
From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [patch 1/1] dmesg: reads /proc/version
Date: Mon, 21 Feb 2011 15:14:21 +0000	[thread overview]
Message-ID: <4D62814D.6010301@redhat.com> (raw)
In-Reply-To: <1298092023.3101.48.camel@tesla.lan>

On 02/19/2011 05:07 AM, Guido Trentalancia wrote:
> Hello Miroslav !
>
> On Fri, 18/02/2011 at 16.00 +0000, Miroslav Grepl wrote:
>> http://mgrepl.fedorapeople.org/F15/admin_dmesg.patch
>>
>>       * dmesg reads /proc/version
>>       * dmesg needs to access to abrt files
> I couldn't find any reference in the source code for dmesg from
> util-linux-ng versions 2.18 and 2.19 about the fact that "dmesg
> reads /proc/version".
>
> Nor I have any indication from the audit logs on the test system I am
> running that dmesg ever required that permission.
>
> Only mount needs to stat() /proc/version.
>
> So, where did you get that from ?
There was a bug saying

type=AVC msg=audit(1293078612.406:8): avc:  denied  { read } for  pid=2405
comm="dmesg" path="/proc/version" dev=proc ino=4026532016
scontext=system_u:system_r:dmesg_t:s0 tcontext=system_u:object_r:proc_t:s0
tclass=file
> And I am not using abrt, but to be honest, I could not find any
> reference to abrt files access either.
>
> Regards,
>
> Guido
>

  reply	other threads:[~2011-02-21 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 16:00 [refpolicy] [patch 1/1] dmesg: reads /proc/version Miroslav Grepl
2011-02-19  5:07 ` Guido Trentalancia
2011-02-21 15:14   ` Miroslav Grepl [this message]
2011-02-21 15:08     ` Guido Trentalancia
2011-02-21 15:33       ` Daniel J Walsh
2011-02-28 14:43         ` 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=4D62814D.6010301@redhat.com \
    --to=mgrepl@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.