From: tom <tom@t0mb.net>
To: Tom Eastep <teastep@shorewall.net>
Cc: netfilter@lists.netfilter.org, vwf <vwf@vulkor.net>
Subject: Re: will --cmd-owner ever return?
Date: Tue, 27 Mar 2007 20:25:34 +0100 [thread overview]
Message-ID: <46096FAE.6060202@t0mb.net> (raw)
In-Reply-To: <460967CB.7020608@shorewall.net>
If a connection is established, then you can find the owner by comparing
the inode in /proc/net/tcp with the /proc/<PID> tree [all the numbered
folders]. In each of these there is a folder named fd which provides
symbolic links to the open file descriptors which that PID is using. a
quick ls -l will give you the information you need to resolve it to a
socket inode, you'll usually see socket:[32424] or something similar.
You then know which PID owns the conection. I have some python code
which resolves this all to program names if you want it?
Tom Eastep wrote:
> vwf wrote:
>
>
>> How can I lock my workstation down on application level?
>>
>
> tuxguardian.sf.net
>
> -Tom
>
next prev parent reply other threads:[~2007-03-27 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 18:45 will --cmd-owner ever return? vwf
2007-03-27 18:51 ` Tom Eastep
2007-03-27 19:25 ` tom [this message]
2007-03-28 2:07 ` Jan Engelhardt
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=46096FAE.6060202@t0mb.net \
--to=tom@t0mb.net \
--cc=netfilter@lists.netfilter.org \
--cc=teastep@shorewall.net \
--cc=vwf@vulkor.net \
/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