In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Nick Maclaren) wrote:
>In article <[EMAIL PROTECTED]>, >Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: >|> In article <[EMAIL PROTECTED]>, >|> Michael Butscher <[EMAIL PROTECTED]> wrote: >|> >|> >Normally any user could connect to an open socket on a machine >|> >regardless which user established the socket (the user's program, to be >|> >precise). >|> >|> That's not true. On *nix systems, a socket is a file, and is subject to >|> the usual file ownership and protection mechanisms. > >I am afraid that BOTH answers are badly wrong! > >Sockets are often accessed via special files, but are not files. They are files. They are not _regular_ files. >They may also be accessed by port numbers, for example. UNIX sockets have no ports. >Secondly, even when they are accessed via files, FIFOs generally >do NOT use the usual file ownership and protection mechanisms to >control access. I wasn't talking about FIFOs. Even if I was, they _are_ still subject to regular file permissions (on Linux, at least). >While any user can attempt to open any socket accessed by port >number... UNIX sockets have no ports. -- http://mail.python.org/mailman/listinfo/python-list
