From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Remote audit clients on RHEL 5.2
Date: Thu, 12 Feb 2009 12:43:03 -0500 [thread overview]
Message-ID: <200902121243.03741.sgrubb@redhat.com> (raw)
In-Reply-To: <499455ED.3060208@groupw.com>
On Thursday 12 February 2009 12:01:33 pm Dan Gruhn wrote:
> I'm not much of a wiz at selinux, but I can tell that the audit_port_t type
> doesn't exist. I'm stuck here because:
>
> 1) I don;t know how to create new types in selinux
> 2) Even if I figured that out, I don't know how auditd would know to use
> that.
>
> I've looked at the auditd executable, it has types like this:
> -rwxr-x--- root root system_u:object_r:auditd_exec_t /sbin/auditd
>
> Could someone give me some pointers and/or point me to something I could
> read to get me going?
You need to be using the SE Linux policy from the 5.3 update. Before 5.3,
auditd never had a listening port and therefore selinux policy prior to it
wouldn't have setup that type. I also think SE Linux policy may default to
port 60 even though that port may not be guaranteed in the future.
Another thing that you should do on this is to setup the client's localport to
bind to a port below 1024 and then set the server's tcp_client_ports to check
that the ports are bound to that range as a security precaution.
-Steve
next prev parent reply other threads:[~2009-02-12 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:01 Remote audit clients on RHEL 5.2 Dan Gruhn
2009-02-12 17:43 ` Steve Grubb [this message]
2009-02-12 17:48 ` Dan Gruhn
2009-02-13 20:11 ` Central Audit Server with Prelude and Prewikka - RHEL5 Dan Gruhn
2009-02-13 20:27 ` Steve Grubb
2009-02-13 21:45 ` Dan Gruhn
[not found] ` <200902121338.50329.sgrubb@redhat.com>
2009-02-17 18:43 ` Remote audit clients on RHEL 5.2 Dan Gruhn
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=200902121243.03741.sgrubb@redhat.com \
--to=sgrubb@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox