[16914] in bugtraq
Re: Patch for esound-0.2.19
daemon@ATHENA.MIT.EDU (James Ralston)
Tue Sep 26 02:29:31 2000
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.4.21.0009251224480.9099-100000@pcmy.sei.cmu.edu>
Date: Mon, 25 Sep 2000 13:32:09 -0400
Reply-To: James Ralston <qralston+ml.bugtraq@ANDREW.CMU.EDU>
From: James Ralston <qralston+ml.bugtraq@ANDREW.CMU.EDU>
X-To: Kris Kennaway <kris@FREEBSD.ORG>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To: <Pine.BSF.4.21.0009231831300.5196-100000@freefall.freebsd.org>
On Sat, 23 Sep 2000, Kris Kennaway wrote:
> FreeBSD fixed this (it was the subject of advisory 00:45) by moving
> the ESD_UNIX_SOCKET_DIR into the user's home directory
In general, it's not a good idea to assume that you can create special
files in the user's home directory.
For example, the AFS distributed filesystem does not implement any
special files (sockets, named pipes, or block or character special
devices). So moving ESD_UNIX_SOCKET_DIR into the user's home
directory, while it might seem like the most straightforward solution,
would simply break esd on systems where a user's home directory is
mounted in AFS.
I haven't inspected esd closely, but I'd guess that this is one of the
reasons why the authors simply didn't locate ESD_UNIX_SOCKET_DIR in
the user's home directory in the first place.
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA