From owner-freebsd-isp Tue Dec 30 20:46:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA00103 for isp-outgoing; Tue, 30 Dec 1997 20:46:16 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29991 for ; Tue, 30 Dec 1997 20:45:58 -0800 (PST) (envelope-from ernie@spooky.eis.net.au) Received: (from ernie@localhost) by spooky.eis.net.au (8.8.7/8.8.3) id OAA10677 for freebsd-isp@freebsd.org; Wed, 31 Dec 1997 14:34:34 +1000 (EST) From: Ernie Elu Message-Id: <199712310434.OAA10677@spooky.eis.net.au> Subject: Virtual Telnet X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: freebsd-isp@freebsd.org Date: Wed, 31 Dec 1997 14:34:33 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] Content-Type: text Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know it is not too hard to set up a virtual domain, website, and ftp site for a client, but is it possible to have a restricted login? By that I mean if you have a freebsd system hosting www.xyz.com and the client wants to be able to telnet in to hand edit files, is it possible to restrict their access to only their home directory and its subdirectories? Sort of an automated chroot thing you can't bypass I guess. - Ernie.