From owner-freebsd-isp Wed Oct 22 15:09:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03235 for isp-outgoing; Wed, 22 Oct 1997 15:09:53 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03211; Wed, 22 Oct 1997 15:09:43 -0700 (PDT) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA13172; Thu, 23 Oct 1997 08:09:25 +1000 (EST) Date: Thu, 23 Oct 1997 08:09:24 +1000 (EST) From: "Daniel O'Callaghan" To: Charles Mott cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Password files and virtual IP addresses In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 22 Oct 1997, Charles Mott wrote: > Suppose that one wanted to create different virtual > IP addresses with ifconfig alias, and when people telnet > or ftp or access pop3/imap2 at a virtual address, a > password file specific to that virtual address would be > used. This would allow username re-use. You *could* do it by hacking getpw*(3) and including a call to getsockname(2). I do it by building virtual machines using a hacked inetd(8) which does a getsockname(2) followed by a chroot(2) to the virtual machine. The vm needs to have ld.so and lib/* etc, etc, etc. It is great for allowing telnet access to web sites while preventing customers from peeking at each other's stuff. /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */