All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: list of permissions created by allow2audit: what do i do now?
Date: Tue, 18 May 2004 12:56:33 +0000	[thread overview]
Message-ID: <20040518125633.GA24917@lkcl.net> (raw)
In-Reply-To: <20040518104026.GC24333@lkcl.net>

On Tue, May 18, 2004 at 10:40:28AM +0000, Luke Kenneth Casson Leighton wrote:

> help, help, i discovered the existence of allow2audit, and _finally_
> i now have a tool that i can use to understand avc messages in terms
> of audit permissions: hooray!
> 
> would someone mind advising me which of these is reasonable/safe
> to allow, or should i just bung them all in and see what happens?

well i tried the bung-it-in-and-see approach, and i got a build error
due to some global policy violations at make policy time because
of this (and one other):

> allow hotplug_t etc_runtime_t:file { relabelfrom relabelto };

... but what is even stranger is that even though i add in these
things into a new package (i called it domains/programs/localstuff.te)
the avc messages _still don't go away_.

i watched the make policy, it read the newly created file
(localstuff.te) and the stuff is in policy.conf.

what am i doing wrong?

l.


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

  parent reply	other threads:[~2004-05-18 12:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 10:40 list of permissions created by allow2audit: what do i do now? Luke Kenneth Casson Leighton
2004-05-18 12:40 ` Stephen Smalley
2004-05-18 13:02   ` Luke Kenneth Casson Leighton
2004-05-18 13:20     ` Stephen Smalley
2004-05-18 13:30       ` Stephen Smalley
2004-05-18 13:44         ` Stephen Smalley
2004-05-18 14:08         ` Luke Kenneth Casson Leighton
2004-05-18 15:11       ` Luke Kenneth Casson Leighton
2004-05-18 17:18         ` Stephen Smalley
2004-05-18 18:51           ` Luke Kenneth Casson Leighton
2004-05-18 19:54             ` Stephen Smalley
2004-05-18 20:18               ` Luke Kenneth Casson Leighton
2004-05-18 20:48             ` Russell Coker
2004-05-18 20:56               ` Luke Kenneth Casson Leighton
2004-05-18 19:51           ` Luke Kenneth Casson Leighton
2004-05-18 18:02         ` Russell Coker
2004-05-18 16:25     ` Valdis.Kletnieks
2004-05-18 19:12       ` Luke Kenneth Casson Leighton
2004-05-18 12:56 ` Luke Kenneth Casson Leighton [this message]
2004-05-18 13:14   ` Stephen Smalley
2004-05-18 15:19     ` Luke Kenneth Casson Leighton
2004-05-18 14:29   ` Russell Coker
2004-05-18 15:30     ` Luke Kenneth Casson Leighton
2004-05-18 14:01 ` Russell Coker

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=20040518125633.GA24917@lkcl.net \
    --to=lkcl@lkcl.net \
    --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.