From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: refpolicy@oss1.tresys.com, selinux@tycho.nsa.gov
Subject: Re: [refpolicy] WARNING: at kernel/printk.c:430 do_syslog+0x40d/0x441()
Date: Wed, 19 Jan 2011 14:23:34 -0500 [thread overview]
Message-ID: <4D373A36.3050504@tresys.com> (raw)
In-Reply-To: <4D372829.5090509@gmail.com>
On 01/19/11 13:06, Justin P. Mattock wrote:
> this is showing up with the latest kernel in enforcing mode..
> (I have not update the policy and/or selinux userspace)
>
> [ 12.803882] type=1400 audit(1295457694.801:3): avc: denied { syslog
> } for pid=1540 comm="rsyslogd" capability=34
> scontext=system_u:system_r:init_t:s0
> tcontext=system_u:system_r:init_t:s0 tclass=capability2
[cut]
> when using audit2allow I get:
>
> allow init_t self:capability2 syslog;
>
> which gives an error when trying to install the module, due to the
> policy not knowing what capability2 is
>
> system is ubuntu maverick, if this is already in(refpolicy) then I'll
> pull the latest when I get a chance..
Support for this capability is upstream in refpolicy.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] WARNING: at kernel/printk.c:430 do_syslog+0x40d/0x441()
Date: Wed, 19 Jan 2011 14:23:34 -0500 [thread overview]
Message-ID: <4D373A36.3050504@tresys.com> (raw)
In-Reply-To: <4D372829.5090509@gmail.com>
On 01/19/11 13:06, Justin P. Mattock wrote:
> this is showing up with the latest kernel in enforcing mode..
> (I have not update the policy and/or selinux userspace)
>
> [ 12.803882] type=1400 audit(1295457694.801:3): avc: denied { syslog
> } for pid=1540 comm="rsyslogd" capability=34
> scontext=system_u:system_r:init_t:s0
> tcontext=system_u:system_r:init_t:s0 tclass=capability2
[cut]
> when using audit2allow I get:
>
> allow init_t self:capability2 syslog;
>
> which gives an error when trying to install the module, due to the
> policy not knowing what capability2 is
>
> system is ubuntu maverick, if this is already in(refpolicy) then I'll
> pull the latest when I get a chance..
Support for this capability is upstream in refpolicy.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-01-19 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:06 WARNING: at kernel/printk.c:430 do_syslog+0x40d/0x441() Justin P. Mattock
2011-01-19 18:06 ` [refpolicy] " Justin P. Mattock
2011-01-19 19:23 ` Christopher J. PeBenito [this message]
2011-01-19 19:23 ` Christopher J. PeBenito
2011-01-19 19:30 ` Justin P. Mattock
2011-01-19 19:30 ` Justin P. Mattock
2011-01-24 19:30 ` Justin P. Mattock
2011-01-24 19:30 ` Justin P. Mattock
2011-01-24 19:34 ` Justin P. Mattock
2011-01-24 19:34 ` Justin P. Mattock
2011-01-24 20:27 ` Dominick Grift
2011-01-24 20:57 ` Justin P. Mattock
2011-01-24 21:03 ` Dominick Grift
2011-01-24 21:08 ` Justin P. Mattock
2011-01-24 22:39 ` Justin P. Mattock
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=4D373A36.3050504@tresys.com \
--to=cpebenito@tresys.com \
--cc=justinmattock@gmail.com \
--cc=refpolicy@oss1.tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.