Re: How to check UID of process on the other side of local TCP/UDP connection
Luciano Miguel Ferreira Rocha <[email protected]> Wed, 29 Nov 2006 20:57:56 +0000
| Newsgroups | gmane.comp.security.linux |
|---|---|
| Message-ID | <[email protected]> |
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
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQFFbfRUinSul6a7oB8RAke2AJ99Ibq53HwQS1SBlGFIsZs+i+Q6WgCgovSd MTuRubX+5ujVeJXaQOg3iBA= =wrr5 -----END PGP SIGNATURE-----