From owner-freebsd-isp Wed Nov 3 9:28:34 1999 Delivered-To: freebsd-isp@freebsd.org Received: from iwill.win.net (iwill.win.net [216.24.1.213]) by hub.freebsd.org (Postfix) with ESMTP id 73B7A14E61 for ; Wed, 3 Nov 1999 09:28:24 -0800 (PST) (envelope-from kstone@win.net) Received: from localhost (stone@localhost) by iwill.win.net (8.9.3/8.9.3) with ESMTP id RAA31781 for ; Wed, 3 Nov 1999 17:28:33 GMT (envelope-from kstone@win.net) From: kstone@win.net X-Authentication-Warning: iwill.win.net: stone owned process doing -bs Date: Wed, 3 Nov 1999 17:28:33 +0000 (GMT) X-Sender: stone@iwill.win.net To: freebsd-isp@FreeBSD.ORG Subject: NIS/Radius, LDAP/K5, etc.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm in the process of determining what sort of centralized user auth to implament. I currently need to provide authentication for POP3, dial-up, shell access, and provide UID/GIDS, etc to processes like Apache. These auth/account info services should also be redundant, replicatable and encrypted enough for use across a WAN. Anyone have suggestions as to what I should use for auth and account info distribution? Kyle Stone kstone@win.net System Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message