All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 0/7] Updates on zabbix service
Date: Mon, 13 Jun 2011 10:20:06 +0200	[thread overview]
Message-ID: <20110613082006.GA18072@siphos.be> (raw)

Zabbix is an open-source/free software monitoring solution. A module already
exists in the refpolicy, but does not work properly. Also, the module does
not support a different domain for the agents (zabbix agents) although this
is greatly preferred.

The following set of patches introduce the following to this module set:

1. Zabbix server is a multi-process system requiring signals to be sent and
   (exclusive) locks to be taken where needed (for instance used with
   logging)
2. Zabbix servers use posix shared memory (using tmpfs backend), so create a
   zabbix_tmpfs_t domain and allow the server access to manage it
3. Zabbix uses a dedicated port (10051) for its server. Allow the servers to
   bind to it, and of course define it as a specific port in SELinux
4. Start with the definition of the zabbix_agent_t domain
5. Allow zabbix_agent to bind on its own port (10050) and connect to the
   zabbix server (for the regular metric submissions)
6. The zabbix server also needs to connect to the agent (for what Zabbix
   calls "active monitoring")
7. Give zabbix_agent_t the privileges it needs to scan the system (get
   system state, read files, check services, ...)

Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>

             reply	other threads:[~2011-06-13  8:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  8:20 Sven Vermeulen [this message]
2011-06-13  8:25 ` [refpolicy] [PATCH 1/7] zabbix server spawns multiple processes Sven Vermeulen
2011-06-13  8:28   ` [refpolicy] [PATCH 2/7] Support shared memory Sven Vermeulen
2011-06-13  8:29     ` [refpolicy] [PATCH 3/7] Define zabbix port and allow server to listen/bind on it Sven Vermeulen
2011-06-13  8:31       ` [refpolicy] [PATCH 4/7] Support different domain for zabbix agent (start with skeleton) Sven Vermeulen
2011-06-13  8:34         ` [refpolicy] [PATCH 5/7] Zabbix agent binds on its own port, connects to zabbix server Sven Vermeulen
2011-06-13  8:35           ` [refpolicy] [PATCH 6/7] Allow zabbix server to connect to agent (active monitoring) Sven Vermeulen
2011-06-13  8:40             ` [refpolicy] [PATCH 7/7] Allow zabbix agent to query system state and other monitorable aspects Sven Vermeulen
2011-06-15 13:26               ` Christopher J. PeBenito
2011-06-15 16:59               ` Sven Vermeulen
2011-06-13 10:14             ` [refpolicy] [PATCH 6/7] Allow zabbix server to connect to agent (active monitoring) Sven Vermeulen
2011-06-15 16:58             ` Sven Vermeulen
2011-06-13 10:13           ` [refpolicy] [PATCH 5/7] Zabbix agent binds on its own port, connects to zabbix server Sven Vermeulen
2011-06-15 16:57           ` Sven Vermeulen
     [not found]         ` <20110613101151.GB26655@siphos.be>
2011-06-13 10:22           ` [refpolicy] [PATCH 4/7] Support different domain for zabbix agent (start with skeleton) Sven Vermeulen
2011-06-15 16:56         ` Sven Vermeulen
2011-06-13 10:10     ` [refpolicy] [PATCH 2/7] Support shared memory Sven Vermeulen
2011-06-15 18:20 ` [refpolicy] [PATCH 0/7] Updates on zabbix service Christopher J. PeBenito

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=20110613082006.GA18072@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.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.