All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Heinrich Kiwi <klausk@br.ibm.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH 00/07][RFC] RACF audit plugin
Date: Fri, 28 Sep 2007 21:09:20 +0000 (UTC)	[thread overview]
Message-ID: <fdjqi0$vk2$1@sea.gmane.org> (raw)
In-Reply-To: 1190986087.4113.49.camel@klausk.br.ibm.com

On Fri, 28 Sep 2007 10:28:07 -0300, Klaus Heinrich Kiwi wrote:

> TODO list:
> ==========
> - SELinux policy (currently, the plugin runs under the audit daemon
> domain, which denies some network operations, for example)

Steve,

  you mentioned in an IRC chat that dwalsh has made a nice GUI tool for 
building new policy - can you point it out??

Dan mentioned we would need a policy module that gets loaded by a post-
install script upon the plugin installation. The policy module would 
define 'racf_t' and 'racf_exec_t' types, and the 'racf_exec_t'-labeled 
plugin would then transition to it's own 'racf_t' domain upon execution. 
Transition would be allowed by the 'racf_domtrans(auditd_t)' interface.

As for 'racf_t' permissions, I need LDAP and DNS access. Reading the AVC 
messages I saw I may need:
tcp_socket {read write shutdown name_connect connect setop create}
udp_socket {read write getattr connect create}
netlink_route_socket { nlmsg_read, read }

Anyone knows if this set of permissions are implemented by a more-generic 
policy interface? Dan?

Thanks!

 Klaus K

  parent reply	other threads:[~2007-09-28 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 13:28 [PATCH 00/07][RFC] RACF audit plugin Klaus Heinrich Kiwi
2007-09-28 18:47 ` Steve Grubb
2007-09-28 19:42   ` Klaus Heinrich Kiwi
2007-09-28 20:01     ` Steve Grubb
2007-09-28 20:18       ` Klaus Heinrich Kiwi
2007-09-28 21:09 ` Klaus Heinrich Kiwi [this message]
2007-09-28 22:43   ` Steve Grubb

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='fdjqi0$vk2$1@sea.gmane.org' \
    --to=klausk@br.ibm.com \
    --cc=linux-audit@redhat.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.