From owner-freebsd-hackers  Wed Sep 22  7: 3:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 4CF1F14A0A
	for <hackers@FreeBSD.org>; Wed, 22 Sep 1999 07:03:42 -0700 (PDT)
	(envelope-from freebsd-hackers@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id PAA96390
	for hackers@FreeBSD.org; Wed, 22 Sep 1999 15:33:46 +0200 (CEST)
	(envelope-from freebsd-hackers@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for hackers@FreeBSD.org (hackers@FreeBSD.org)
To: hackers@FreeBSD.org
Date: Wed, 22 Sep 1999 15:33:44 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37E8DAB8.B7F50BA9@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <37E8D481.5A8C484A@cequrux.com>
Subject: Re: Domain sockets and chroot
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Graham Wheeler wrote:

> The server creates a domain socket to listen for requests with the
> path /cage/tmp/server. The client runs chrooted in the /cage directory,
> and creates a domain socket /tmp/client.<pid>. It sends a request to
> the server with a sendto() specifying the socket address /tmp/server.
> The server received the request okay, but gets the sender socket address
> /tmp/client.<pid> ; i.e. it is the chrooted view of the client socket.
> If it tries to send back a response, it fails (no such file or
> directory).

What about?

	cd /cage
	ln -s / cage

And let the client specify /cage/tmp/client.<pid>

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message