Re: How to check UID of process on the other side of local TCP/UDP connection
- From: Filipe Varela <fcv@xxxxxxxx>
- Date: Tue, 28 Nov 2006 17:17:09 +0000
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?
Thanks for reading
Filipe
- Follow-Ups:
- Re: How to check UID of process on the other side of local TCP/UDP connection
- From: Luciano Miguel Ferreira Rocha
- Re: How to check UID of process on the other side of local TCP/UDP connection
- From: Glynn Clements
- Re: How to check UID of process on the other side of local TCP/UDP connection
- From: Vladimir Mitiouchev
- Re: How to check UID of process on the other side of local TCP/UDP connection
- References:
- How to check UID of process on the other side of local TCP/UDP connection
- From: rainmailbox2001-ola
- Re: How to check UID of process on the other side of local TCP/UDP connection
- From: Luciano Miguel Ferreira Rocha
- How to check UID of process on the other side of local TCP/UDP connection
- Prev by Date: RE: Red Hat vs Debian Linux: overall security
- Next by Date: Re: How to check UID of process on the other side of local TCP/UDP connection
- Previous by thread: Re: How to check UID of process on the other side of local TCP/UDP connection
- Next by thread: Re: How to check UID of process on the other side of local TCP/UDP connection
- Index(es):
Relevant Pages
|
|