All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Caplan <dac@tresys.com>
To: "Magosányi Árpád" <mag@bunuel.tii.matav.hu>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: dumb auditdeny question
Date: Wed, 11 Feb 2004 08:58:29 -0500	[thread overview]
Message-ID: <402A3505.2030809@tresys.com> (raw)
In-Reply-To: <1076486595.2415.134.camel@kusturica>

Magosányi Árpád wrote:
> Hi!
> 
> I wanted to get rid of the following message:
> 
>  avc:  denied  { create } for  pid=400 exe=/usr/bin/vim
> scontext=kernel_u:kernel_r:kernel_d tcontext=kernel_u:object_r:tcb_t
> tclass=file
> 
> so I have the following in my policy:
> 
> auditdeny kernel_d tcb_t:{ file lnk_file sock_file fifo_file chr_file }
>         { ioctl append rename create };
> 
> But I still get the message.
> 
> What did I do wrong?
> 

You want to use the "dontaudit" command.  Auditdeny says to generate a 
message only when permission was denied on the specified access.  So you 
probably want:

dontaudit kernel_d tcb_t:{ file lnk_file sock_file fifo_file chr_file } 
            { ioctl append rename create };

It's not a dumb question; the auditdeny keyword is confusing.  That's 
one reason the dontaudit syntax was introduced.  I believe in the base 
(NSA) policy there are no uses of auditdeny.

David

__________________________________

David Caplan     410 290 1411 x105
dac@tresys.com
Tresys Technology, LLC
8840 Stanford Blvd., Suite 2100
Columbia, MD 21045

--
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-02-11 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11  8:03 dumb auditdeny question Magosányi Árpád
2004-02-11 12:31 ` Faye Coker
2004-02-11 13:58 ` David Caplan [this message]

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=402A3505.2030809@tresys.com \
    --to=dac@tresys.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=mag@bunuel.tii.matav.hu \
    /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.