[4541] in bugtraq
Re: UNIX domain socket (Solarisx86 2.5)
daemon@ATHENA.MIT.EDU (Charles M. Hannum)
Wed May 21 19:21:50 1997
Date: Wed, 21 May 1997 12:08:07 -0400
Reply-To: "Charles M. Hannum" <mycroft@GNU.AI.MIT.EDU>
From: "Charles M. Hannum" <mycroft@GNU.AI.MIT.EDU>
X-To: Casper Dik <casper@HOLLAND.SUN.COM>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: Casper Dik's message of Wed, 21 May 1997 11:17:54 +0200
Casper Dik <casper@HOLLAND.SUN.COM> writes:
>
> The placeholder for a Unix domain socket in Solaris is a mode 0 pipe.
> (Though in 2.6 this changes and sockets are again first class citizens)
> As stated in the original unix domain socket documentation "the filesystem
> entry is an artifact of the implementation" or words to that effect.
You'll note that's been changed in 4.4BSD:
Normal
filesystem access-control mechanisms are also applied when referencing
pathnames; e.g., the destination of a connect(2) or sendto(2) must be
writable.
I believe there are other systems which do this as well, and arguably
it's the desired behaviour. However, portable programs can't rely on
it.
