1996-01-24 - Associating Local Port Number to PID

Header Data

From: “Karl A. Siil” <karl@cosmos.cosmos.att.com>
To: cypherpunks@toad.com
Message Hash: c67c2ee4285ede8e393a30ba6c15f4c6820e19423608ce7037ed294c6bb56b50
Message ID: <2.2.32.19960124164913.006a5fa0@cosmos.cosmos.att.com>
Reply To: N/A
UTC Datetime: 1996-01-24 17:38:23 UTC
Raw Date: Thu, 25 Jan 1996 01:38:23 +0800

Raw message

From: "Karl A. Siil" <karl@cosmos.cosmos.att.com>
Date: Thu, 25 Jan 1996 01:38:23 +0800
To: cypherpunks@toad.com
Subject: Associating Local Port Number to PID
Message-ID: <2.2.32.19960124164913.006a5fa0@cosmos.cosmos.att.com>
MIME-Version: 1.0
Content-Type: text/plain


Folks,

I'm working on a program for UNIX (SVR4, Solaris 2.4) systems that needs to
associate PID with local TCP/IP port number, so as to pass session keys
accordingly to already running processes. This sounds like such an obviously
needed association that someone must have done it already.

Pointers to code would be best, but any references would be helpful (e.g.,
the appropriate /dev/kmem data structure(s), offset(s), etc.). If necessary,
the program is allowed to be in any group (e.g., "sys" to get at /dev/kmem)
and may even run as root, as a last resort. I see no reason for the latter,
however. Running set-gid to "sys" is sufficient for netstat(1) and ps(1) and
I think is the upper bound for process privilege that I would need.

Thanks in advance.

                                        Karl






Thread