public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Get source and destination info
@ 2007-09-02 23:18 Shahbaz Khan
  2007-09-02 23:30 ` Casey Schaufler
  0 siblings, 1 reply; 2+ messages in thread
From: Shahbaz Khan @ 2007-09-02 23:18 UTC (permalink / raw)
  To: linux-kernel, selinux

Hi,

I am trying to figure out what part in the kernel code is the point
from where I can get source and destination ip-address, port, security
labels (selinux etc) from a packet before I export it to application
space for my needs. Any hints?

Shaz.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Get source and destination info
  2007-09-02 23:18 Get source and destination info Shahbaz Khan
@ 2007-09-02 23:30 ` Casey Schaufler
  0 siblings, 0 replies; 2+ messages in thread
From: Casey Schaufler @ 2007-09-02 23:30 UTC (permalink / raw)
  To: Shahbaz Khan, linux-kernel, selinux


--- Shahbaz Khan <shaz.linux@gmail.com> wrote:

> Hi,
> 
> I am trying to figure out what part in the kernel code is the point
> from where I can get source and destination ip-address, port, security
> labels (selinux etc) from a packet before I export it to application
> space for my needs. Any hints?

Look into the netlabel and xfrm code. In Smack it gets dealt with
in smack_lsm.c, but Smack only uses netlabel. SELinux spreads the
handling into a number of files, including hooks.c, netlabel.c, xfrm.c,
and ss/services.c.


Casey Schaufler
casey@schaufler-ca.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-09-02 23:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-02 23:18 Get source and destination info Shahbaz Khan
2007-09-02 23:30 ` Casey Schaufler

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox