From: Tobias DiPasquale <codeslinger@gmail.com>
To: Nick Hay <nickjhay@hotmail.com>
Cc: nf-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: Extending LOG target to display pid
Date: Tue, 5 Jul 2005 13:28:59 -0400 [thread overview]
Message-ID: <876ef97a05070510285a43128@mail.gmail.com> (raw)
In-Reply-To: <42CAAFE2.3050606@hotmail.com>
On 7/5/05, Nick Hay <nickjhay@hotmail.com> wrote:
> 2. Any ideas on how I can get the pid of a local packet's creator in the
> log module? I couldn't find any structures connected to the sk_buff
> that might contain it, and couldn't think of where the data would
> originally come from.
A security framework, with the proper auditing and accounting
mechanisms in place in the network stack could make this possible (any
it may already be). But in general, it would be quite a lot of work to
add the necessary code to the stack to account for the
sending/receiving PID at the correct stage. Unless you're doing MAC,
its probably not worth it.
> Actually... would current->pid work?
No, because there's no guarantee that the same process is on the CPU
by the time the packet hits your rule.
Can't check on #1 right now, but I believe that its filled in by the
module itself in whatever way it chooses.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next prev parent reply other threads:[~2005-07-05 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 16:05 Extending LOG target to display pid Nick Hay
2005-07-05 17:28 ` Tobias DiPasquale [this message]
2005-07-05 18:05 ` Juha Heljoranta
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 23:56 Nick Hay
2005-07-07 6:32 ` Jonas Berlin
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=876ef97a05070510285a43128@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nickjhay@hotmail.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.