From: Tilman Baumann <tilman.baumann@collax.com>
To: Paul Moore <paul.moore@hp.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>,
linux-security-module@vger.kernel.org
Subject: Re: SMACK netfilter smacklabel socket match
Date: Fri, 26 Sep 2008 14:35:12 +0200 [thread overview]
Message-ID: <48DCD700.7030706@collax.com> (raw)
In-Reply-To: <200809251426.58179.paul.moore@hp.com>
Paul Moore wrote:
> [NOTE: you may notice the above code changing slightly in future
> kernels, it turns out that skb->sk == NULL is not a true indicator of a
> non-local sender, see my labeled networking patches for 2.6.28 or
> linux-next for the revised approach]
Can you give me a pointer where to look?
Will this mean that skb->sk may be invalid or that it will point to a a
context based on the network label the packet has?
In the later case, being able to match remote labels in my match would
just give added benefit. (Though a netlabel (CIPSO) match would probably
be more sane than a smack specific match.)
One would just have more choices where to put a rule like this. Like in
the FORWARD chain.
If non local packets are of no interest, one could put the rule in the
right chain.
But i think i just misunderstood you here. Since having a socket for non
local packets is probably not what you meant.
Regards
Tilman
--
Tilman Baumann
Software Developer
Collax GmbH . Boetzinger Strasse 60 . 79111 Freiburg . Germany
p: +49 (0) 89-990157-0
f: +49 (0) 89-990157-11
Geschaeftsfuehrer: William K. Hite / Boris Nalbach
AG Muenchen HRB 158898, Ust.-IdNr: DE 814464942
next prev parent reply other threads:[~2008-09-26 12:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 17:25 SMACK netfilter smacklabel socket match Tilman Baumann
2008-09-25 18:26 ` Paul Moore
2008-09-25 19:26 ` Tilman Baumann
2008-09-25 19:57 ` Paul Moore
2008-09-25 20:32 ` Tilman Baumann
2008-09-26 12:35 ` Tilman Baumann [this message]
2008-09-26 19:55 ` Paul Moore
2008-09-26 3:43 ` Casey Schaufler
2008-09-26 8:19 ` Tilman Baumann
2008-09-27 5:01 ` Casey Schaufler
2008-09-29 16:21 ` Tilman Baumann
2008-09-30 3:29 ` Casey Schaufler
2008-10-01 11:29 ` Tilman Baumann
2008-10-01 15:21 ` Casey Schaufler
2008-10-01 16:55 ` Tilman Baumann
2008-10-01 18:22 ` Casey Schaufler
2008-10-06 12:57 ` Tilman Baumann
2008-10-06 23:05 ` Ahmed S. Darwish
2008-10-07 2:42 ` Casey Schaufler
2008-10-17 16:57 ` Tilman Baumann
2008-10-17 17:53 ` Casey Schaufler
2008-10-20 12:06 ` Tilman Baumann
2008-10-20 15:01 ` Casey Schaufler
2008-10-22 3:36 ` Casey Schaufler
2008-10-30 16:06 ` Tilman Baumann
2008-10-31 3:46 ` Casey Schaufler
2008-12-11 0:03 ` Casey Schaufler
2008-12-11 10:18 ` Tilman Baumann
2008-12-11 16:29 ` Casey Schaufler
2008-10-23 11:55 ` 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=48DCD700.7030706@collax.com \
--to=tilman.baumann@collax.com \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul.moore@hp.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.