Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Linux
[Top] [All Lists]

Re: How to check UID of process on the other side of local TCP/UDP conne

Subject: Re: How to check UID of process on the other side of local TCP/UDP connection
Date: Wed, 29 Nov 2006 20:13:37 +0000

Filipe Varela wrote:

Anyways, I would prefer to stick with TCP/UDP, because this is  
what my
programs use already, and  I don't really want to change  
everything to
Unix sockets (unless of course Unix sockets are the only good way to
resolve my problems).

I don't want to go off-topic but i have an important question. Isn't  
a socket a concept that translates an address and port? How would  
someone go about doing tcp/udp without sockets when they both depend  
on address/port mappings which are _literally_ sockets?

Am i wrong?

I think that you misunderstood.

By "Unix sockets", he was referring to using Unix-domain sockets
(AF_LOCAL) rather than TCP/IP sockets (AF_INET).

Unix-domain sockets have the advantage that you can obtain the
identity (PID, UID, GID) of the peer from the OS.

-- 
Glynn Clements <glynn@gclements.plus.com>

<Prev in Thread] Current Thread [Next in Thread>