All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nerazzurri.YANG" <spng.yang@gmail.com>
To: Karl MacMillan <kmacmillan@mentalrootkit.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: some errors in installing pp
Date: Sat, 24 Mar 2007 20:53:22 +0800	[thread overview]
Message-ID: <46051F42.6010805@gmail.com> (raw)
In-Reply-To: <1174682887.3169.3.camel@localhost.localdomain>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030; format=flowed, Size: 2723 bytes --]

Karl MacMillan wrote:
> On Fri, 2007-03-23 at 12:28 -0400, Stephen Smalley wrote:
>> On Fri, 2007-03-23 at 11:51 -0400, Karl MacMillan wrote:
>>> On Fri, 2007-03-23 at 08:34 -0400, Stephen Smalley wrote:
>>>> On Fri, 2007-03-23 at 14:33 +0800, Nerazzurri.YANG wrote:
>>>>> 	type self;
>>>> Remove the 'type self;' line.  Did you add that manually or was it
>>>> generated by the new audit2allow?  If the latter, that is a bug.
>>>>
>>> That is a strange bug (if it is - I can't reproduce locally):
>>>
>>> * The way audit2allow works is that self is never stored in the rules,
>>> it is only converted at the point it is output. I did that specifically
>>> to avoid having to special case for self. So it should never add self as
>>> a require.
>>>
> 
> Oops - this is what I wanted to do, but it is not actually possible.
> With multiple source types you can't detect self at output time.
> 
>>> * None of the rules reference self.
>>>
>>> So, if this was generated by audit2allow could you give me the rpm
>>> version for policycoreutils and the log file that generated the policy.
>> Reproduced with latest upstream version, via:
>> # audit2allow -a -r | grep self
>>         type self;
>> allow netutils_t self:capability sys_module;
> 
> Patch below fixes this.


sorry to reply late, you know it's weekend, and we are in different
time zone.

it seems that the problem has been resolved. i will apply the patch
and try again.

but i will still give the info you ask, i think it's helpful for you.

i am in fc7 rawhide (test3 6.92).
the rpm version of policycoreutils is: policycoreutils-2.0.7-4.fc7

now that there is patch for the problem, so i will not attach the log
file, it's so big.

by the way, the reason i use audit2allow to generate pp, it's to resolve
the problem of mono(beagle), i have sent the details to
"fedora-selinux-list", and Mr walsh has posted it to the list.

anyway, thank you very much



> 
> Signed-off-by: Karl MacMillan <kmacmillan@mentalrootkit.com>
> 
> diff -r 597d85c85841 sepolgen/src/sepolgen/policygen.py
> --- a/sepolgen/src/sepolgen/policygen.py	Wed Mar 21 16:38:20 2007 -0400
> +++ b/sepolgen/src/sepolgen/policygen.py	Fri Mar 23 16:44:05 2007 -0400
> @@ -334,6 +334,8 @@ def gen_requires(module):
>                  # can actually figure those out.
>                  r.types.add(arg)
>  
> +        r.types.discard("self")
> +                
>          node.children.insert(0, r)
>  
>      # FUTURE - this is untested on modules with any sort of
> 
> 
> 


--
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.

  reply	other threads:[~2007-03-24 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23  6:33 some errors in installing pp Nerazzurri.YANG
2007-03-23 12:34 ` Stephen Smalley
2007-03-23 15:51   ` Karl MacMillan
2007-03-23 16:28     ` Stephen Smalley
2007-03-23 16:43       ` Stephen Smalley
2007-03-23 16:45         ` Stephen Smalley
2007-03-23 20:48       ` Karl MacMillan
2007-03-24 12:53         ` Nerazzurri.YANG [this message]
2007-03-26 14:52           ` Karl MacMillan
2007-03-26 15:03         ` Stephen Smalley

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=46051F42.6010805@gmail.com \
    --to=spng.yang@gmail.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=sds@tycho.nsa.gov \
    --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.