Date: Tue, 10 Sep 1996 04:44:48 -0500 (CDT) From: Tony Kimball <alk@think.com> To: richard@thehub.com.au Cc: freebsd-isp@freebsd.org Subject: Recommendations on password management. Message-ID: <199609100944.EAA16704@compound.Think.COM> References: <Pine.BSF.3.91.960910180927.5852C-100000@smople.thehub.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609100944.EAA16704>