Bugtraq mailing list archives
Re: UNIX domain socket (Solarisx86 2.5)
From: mycroft () GNU AI MIT EDU (Charles M. Hannum)
Date: Wed, 21 May 1997 12:08:07 -0400
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.
Current thread:
- UNIX domain socket (Solarisx86 2.5) Thamer Al-Herbish (May 17)
- Re: UNIX domain socket (Solarisx86 2.5) Joel Murphy (May 20)
- Re: UNIX domain socket (Solarisx86 2.5) Casper Dik (May 21)
- Re: UNIX domain socket (Solarisx86 2.5) Vic Abell (May 21)
- Re: UNIX domain socket (Solarisx86 2.5) Alan Cox (May 21)
- CERT Advisory CA-97.14 - Vulnerability in metamail Aleph One (May 21)
- TrueBasic/Mac Bug Xservo (May 21)
- Re: UNIX domain socket (Solarisx86 2.5) Casper Dik (May 21)
- <Possible follow-ups>
- Re: UNIX domain socket (Solarisx86 2.5) Charles M. Hannum (May 21)
- Re: UNIX domain socket (Solarisx86 2.5) Joel Murphy (May 20)