From: James Morris <jmorris@namei.org>
To: "Török Edwin" <edwin.torok@level7.ro>
Cc: netfilter-devel@lists.netfilter.org,
fireflier-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, martinmaurer@gmx.at,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
Date: Mon, 20 Feb 2006 15:06:41 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602201502220.21834@excalibur.intercode> (raw)
In-Reply-To: <200602201940.40504.edwin.torok@level7.ro>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1525 bytes --]
On Mon, 20 Feb 2006, Török Edwin wrote:
> In the following I will be referring to 16-skfilter-ipt_owner-ctx.patch:
>
> However I'd like to do filtering based on owner (process) even when selinux is
> not available. Your context match explicitly requires selinux to be enabled,
> and a policy loaded.
See at 10-skfilter-incoming-ipt_owner.patch, which enables incoming
matching based on socket owner, not related to SELinux.
> Could you please use LSM hooks (like inode_getsecurity) instead of directly
> using selinux? I'd want to provide my own implementation of labeling (a
> very,very simple labeling, a very small subset of what selinux does, but
> which wouldn't require much configuration). In other words, I want to write a
> LSM, and then mod_register_security() my module.
>
> Or if the above is not possible, could you provide some hooks, where I could
> register my hooks to provide these:
> - int available()
> - int ctx_to_id(char*,u32*)
> - int socket_to_ctxid(struct sock*,u32*)
>
> (Of course I could create another match that would use my module to do the
> matching on the SOCKET chain. But this would uselessly duplicate
> functionality&code, an additional hook would be a much cleaner solution).
>
> What is your opinion on what I said above? I am open to suggestions,
> criticism, advice....
It's possible to investigate doing this via LSM, although probably not
justified unless someone else is using this feature in the mainline tree.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2006-02-20 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 12:10 Török Edwin
2006-02-18 12:25 ` Christoph Hellwig
2006-02-18 12:32 ` Török Edwin
2006-02-18 12:37 ` Christoph Hellwig
2006-02-18 12:47 ` Török Edwin
2006-02-18 13:10 ` Arjan van de Ven
2006-02-18 14:15 ` Török Edwin
2006-02-20 16:26 ` James Morris
2006-02-20 16:42 ` Patrick McHardy
2006-02-20 17:40 ` Török Edwin
2006-02-20 20:06 ` James Morris [this message]
2006-02-18 12:20 Török Edwin
2006-02-18 19:28 ` Patrick McHardy
2006-02-18 20:03 ` Török Edwin
2006-02-18 20:07 ` Patrick McHardy
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=Pine.LNX.4.64.0602201502220.21834@excalibur.intercode \
--to=jmorris@namei.org \
--cc=edwin.torok@level7.ro \
--cc=fireflier-devel@lists.sourceforge.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martinmaurer@gmx.at \
--cc=netfilter-devel@lists.netfilter.org \
/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
Powered by JetHome