From: Daniel J Walsh <dwalsh@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: Eric Paris <eparis@parisplace.org>,
Karl MacMillan <kmacmillan@mentalrootkit.com>,
selinux@tycho.nsa.gov, Joshua Brindle <method@manicmethod.com>
Subject: Re: secmark integration
Date: Mon, 02 Apr 2007 10:45:29 -0400 [thread overview]
Message-ID: <46111709.9060402@redhat.com> (raw)
In-Reply-To: <Line.LNX.4.64.0703302201520.29742@d.namei>
James Morris wrote:
> On Fri, 30 Mar 2007, Eric Paris wrote:
>
>
>>> Is this really needed as long as the distro provides a way to customize
>>> the iptables rules?
>>>
>> It's not just that. The reason a new table was proposed was because
>> people may want to iptables -F and flush their rules. If the secmark
>> stuff is on the main tables (filter and nat) that people use it will get
>> blown away and there will be no automation of a boolean setting you talk
>> about later.
>>
>
> I think there's also a good case for a separate table on the basis that
> the rules are part of a separate administrative realm (e.g. MAC, rather
> than DAC) and should be maintained separately. We could also look at
> adding an LSM hook for rules being manipulated in this table (perhaps
> called 'security' to be more general).
>
> Note that there may be tools which parse /proc/net/ip_tables_names when
> flushing (which the LSM hook would possibly help with in terms of stopping
> MAC policy from being modified without the correct authorization).
>
> It still may be difficult to sell upstream, so we'd need more feedback
> from the distro folk possibly after some experimentation.
>
>
> - James
>
I like karl suggestion. service iptables stop , flips boolean that says
all domains support unlabeled_t:packet. service iptables start turns
that off.
Currently there is a boolean in Rawhide allow_unlabeled_packets.
tunable_policy(`allow_unlabeled_packets',`
kernel_sendrecv_unlabeled_association(domain)
corenet_sendrecv_unlabeled_packets(domain)
')
These lines endup generating these rules
allow domain unlabeled_t:packet { send recv };
allow domain $1 unlabeled_t:association { sendto recvfrom };
This boolean defaults to true.
I think as soon as FC7 ships we can start experimenting in Rawhide and
build a couple of scripts/modules that people could use to take
advantage of secmark.
--
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-04-02 14:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 14:57 secmark integration James Morris
2007-03-30 19:47 ` Karl MacMillan
2007-03-30 20:25 ` Eric Paris
2007-03-30 20:36 ` Karl MacMillan
2007-03-30 21:47 ` Eric Paris
2007-04-02 17:23 ` Karl MacMillan
2007-04-02 19:44 ` James Morris
2007-03-31 2:09 ` James Morris
2007-04-02 14:45 ` Daniel J Walsh [this message]
2007-04-02 14:55 ` Eric Paris
2007-04-02 15:15 ` Christopher J. PeBenito
2007-04-02 17:15 ` Karl MacMillan
2007-04-04 17:22 ` Christopher J. PeBenito
2007-04-04 20:08 ` Karl MacMillan
2007-04-04 20:51 ` Daniel J Walsh
2007-04-05 15:48 ` Karl MacMillan
2007-04-05 17:06 ` Christopher J. PeBenito
2007-04-05 17:40 ` Karl MacMillan
2007-04-05 17:47 ` Stephen Smalley
2007-04-05 18:02 ` Christopher J. PeBenito
2007-04-05 17:59 ` Stephen Smalley
2007-04-05 18:46 ` Christopher J. PeBenito
2007-04-05 18:48 ` Joshua Brindle
2007-04-05 19:22 ` Stephen Smalley
2007-04-05 19:53 ` Eamon Walsh
2007-04-05 19:59 ` Stephen Smalley
2007-04-05 18:49 ` Stephen Smalley
2007-04-02 16:16 ` James Morris
2007-04-02 17:14 ` Joshua Brindle
2007-04-02 17:28 ` Karl MacMillan
2007-04-02 19:47 ` James Morris
2007-04-02 19:52 ` Karl MacMillan
2007-04-02 14:52 ` Paul Moore
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=46111709.9060402@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=kmacmillan@mentalrootkit.com \
--cc=method@manicmethod.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.