From owner-freebsd-isp Tue Sep 10 02:49:05 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05222 for isp-outgoing; Tue, 10 Sep 1996 02:49:05 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05217 for ; Tue, 10 Sep 1996 02:49:02 -0700 (PDT) Received: from Early-Bird.Think.COM (Early-Bird-1.Think.COM [131.239.146.105]) by mail.think.com (8.7.5/m3) with ESMTP id FAA14207; Tue, 10 Sep 1996 05:48:43 -0400 (EDT) Received: from compound.Think.COM (fergus-2.dialup.prtel.com [206.10.99.132]) by Early-Bird.Think.COM (8.7.5/e1) with ESMTP id FAA11585; Tue, 10 Sep 1996 05:48:13 -0400 (EDT) Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id EAA16704; Tue, 10 Sep 1996 04:44:48 -0500 (CDT) Date: Tue, 10 Sep 1996 04:44:48 -0500 (CDT) From: Tony Kimball Message-Id: <199609100944.EAA16704@compound.Think.COM> To: richard@thehub.com.au Cc: freebsd-isp@freebsd.org Subject: Recommendations on password management. References: Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Richard J. Uren on Tue, 10 September: : Im thinking of something like a master node where all passowrd changes : are made and leaf nodes which perform the username/password lookups for : local stuff (popper & ftp & radius ..). : : The central node would also handle user accounting etc .... as well. : Any suggestions on the best way to meet these requirements ? : cron rsync in a tree (if your net topo is stable, degnerate to star in the worst case) to keep passwd current. when supporting naive clients, you may wish to handle passwd changes by a mail processor. I can send you one in perl but you would need to modify it to support your authentication model -- should be trivial since your central node gets the connect info anyhow.