|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: How to check UID of process on the other side of local TCP/UDP connection
From: Luciano Miguel Ferreira Rocha (strange
nsk.no-ip.org)
Date: Wed Nov 29 2006 - 14:57:56 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Nov 28, 2006 at 05:17:09PM +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?
I don't really understand your question nor where did the concept of
doing tcp/udp without sockets originated.
Maybe you're misreading the term Unix sockets? Sockets can belong to
different protocol families: INET, INET6, UNIX/LOCAL, X25, etc..
Unix sockets means using sockets for local interprocess communication.
They don't use any network protocol.
man 7 unix
--
lfr
0/0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQFFbfRUinSul6a7oB8RAke2AJ99Ibq53HwQS1SBlGFIsZs+i+Q6WgCgovSd
MTuRubX+5ujVeJXaQOg3iBA=
=wrr5
-----END PGP SIGNATURE-----
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]