linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: akuda <akuda@poczta.fm>
To: linux-admin@vger.kernel.org
Subject: How to inentify local source of connection (program and user)
Date: Sun, 30 Nov 2008 06:06:27 -0800 (PST)	[thread overview]
Message-ID: <20757992.post@talk.nabble.com> (raw)


Hi,

Recently I found some unidentified outgoing connections (UOC, instead of
UFO) from one of my linux machines (gentoo, firewall by vuurmuur.org via
ipTables). Those UOC occurs soon after boot time, even though I closed all
services. These are DNS calls.
   So I asked my friends full-time admins, how to check which program
requests access to internet, and what user started this program. If, for
example, RIAA would come to some University telling that from their IP
someone is downloading "Lilo & Stitch" illegally, the admin should be able
to tell who turned on bittorrent :) . And what stroke me was the fact, that
they actually didn't know! They asked me to hunt for those UOC, and then
type netstat with some options, to get the path to the binary, and locate in
someone's home directory (the bittorrent client won't be probably installed
as general bin for all users :) ).
   Any other idea how to do it? Can I force linux to log who and how is
requesting a outgoing connection?

-- 
View this message in context: http://www.nabble.com/How-to-inentify-local-source-of-connection-%28program-and-user%29-tp20757992p20757992.html
Sent from the linux-admin mailing list archive at Nabble.com.


             reply	other threads:[~2008-11-30 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 14:06 akuda [this message]
2008-11-30 14:38 ` How to inentify local source of connection (program and user) Herta Van den Eynde
2008-11-30 17:02 ` Michael H. Warfield
2008-11-30 18:48 ` Glynn Clements

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=20757992.post@talk.nabble.com \
    --to=akuda@poczta.fm \
    --cc=linux-admin@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).