From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: New fail2ban policy
Date: Tue, 20 Mar 2007 20:01:04 +0000 [thread overview]
Message-ID: <1174420865.16552.3.camel@sgc> (raw)
In-Reply-To: <45F01D96.1010806@redhat.com>
On Thu, 2007-03-08 at 09:28 -0500, Daniel J Walsh wrote:
This seems to have rules similar to iptables:
> +allow fail2ban_t self : capability { net_admin net_raw };
> +allow fail2ban_t self : rawip_socket { getopt create setopt };
But also transitions to iptables?
> +optional_policy(`
> + iptables_domtrans(fail2ban_t)
> +')
This also seems out of place:
> +selinux_get_fs_mount(fail2ban_t)
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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.
next prev parent reply other threads:[~2007-03-20 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 14:28 New fail2ban policy Daniel J Walsh
2007-03-20 20:01 ` Christopher J. PeBenito [this message]
2007-03-20 20:27 ` Daniel J Walsh
2007-03-21 14:47 ` 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=1174420865.16552.3.camel@sgc \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--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.