From: Andrej Ricnik <andrej@paradise.net.nz>
To: netfilter-devel@lists.netfilter.org
Subject: How/where does the kernel map packets to an application ...
Date: Thu, 15 Jan 2004 09:10:30 +1300 [thread overview]
Message-ID: <200401150910.32898.andrej@paradise.net.nz> (raw)
Hi Guys,
and sorry for asking this here, I'm aware of the fact that
this isn't quite the right list to do so, in fact, I don't even
know how to word my question properly, so please bear
with me.
Since you're pretty close to what I suspect to be the right
layer to be looking at I hope someone might understand
what I'm on about :)
My idea is to write an addition to netfilter that will check
the originating application of an IP request against a list
of allowed files, and if I handle that well enough, integrate
a roster of user/application to check whether a request is
legal or not.
My question is:
At which point does the kernel determine which application
a incoming packet is meant for? Imagine one user having
mozilla and opera open, using both for browsing. Another
user having a links session in a console. How does the
kernel determine which application is meant to receive
a incoming packet on port 80? I hope that once I under-
stand how this works I could for instance use lsof or a
tool the like to intercept illegal requests by matching
against application name/path ...
If this is a FAQ, or just plain stupid, please throw me a
link to appropriate documentation.
Thanks in advance, and thanks for your patience,
Cheers,
Tink
next reply other threads:[~2004-01-14 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 20:10 Andrej Ricnik [this message]
2004-01-14 23:48 ` How/where does the kernel map packets to an application Pablo Neira
2004-01-15 7:10 ` Henrik Nordstrom
2004-01-15 19:34 ` Martin Josefsson
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=200401150910.32898.andrej@paradise.net.nz \
--to=andrej@paradise.net.nz \
--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 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.