From owner-freebsd-isp  Thu Jul 15  9:54:44 1999
Delivered-To: freebsd-isp@freebsd.org
Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118])
	by hub.freebsd.org (Postfix) with ESMTP id 7C8031558F
	for <freebsd-isp@FreeBSD.ORG>; Thu, 15 Jul 1999 09:54:31 -0700 (PDT)
	(envelope-from stuart@eclipse.net.uk)
Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31])
	by proteus.eclipse.net.uk (Postfix) with ESMTP
	id 2B5929B01; Thu, 15 Jul 1999 17:53:12 +0100 (BST)
Message-ID: <378E123D.35210708@eclipse.net.uk>
Date: Thu, 15 Jul 1999 17:54:21 +0100
From: Stuart Henderson <stuart@eclipse.net.uk>
Organization: Eclipse Networking Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en-GB
MIME-Version: 1.0
To: Khetan Gajjar <khetan@os.org.za>
Cc: Stephane.Lentz@ansf.alcatel.fr, freebsd-isp@FreeBSD.ORG
Subject: Re: sendmail virtusertable
References: <Pine.BSF.4.02A.9907151744490.4870-100000@pleb.cs.uct.ac.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> As it stands right now, because I partially trust the users
> (there are only 4), they all have read/write access to the
> master virtusertable, but it would be trivial to create
> multiple input virtusertables, cat them together to create the
> master inputfile and rebuild the database periodically.

If you dig through the archives of this list, you'll find a discussion
on this, basically, if you can't trust your users you need to do a
little sanity checking. "cat | grep '@allowed-domain.com '" should show
what I mean, although you would really want something more robust than
this (far too easy to break :-) 

I would also recommend building your db files to a new file, and check 
they have built OK before using them for real (at very least make sure 
they're not zero bytes).


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