From owner-freebsd-security Mon Feb 26 13:21:45 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17584 for security-outgoing; Mon, 26 Feb 1996 13:21:45 -0800 (PST) Received: from zip.io.org (root@zip.io.org [198.133.36.80]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA17572 for ; Mon, 26 Feb 1996 13:21:41 -0800 (PST) Received: (from taob@localhost) by zip.io.org (8.6.12/8.6.12) id QAA04587; Mon, 26 Feb 1996 16:20:48 -0500 Date: Mon, 26 Feb 1996 16:20:48 -0500 (EST) From: Brian Tao To: William Bulley cc: freebsd-security@freebsd.org Subject: Re: Informing users of cracked passwords? In-Reply-To: <199602262117.QAA09158@ohm.merit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org Precedence: bulk On Mon, 26 Feb 1996, William Bulley wrote: > > I would recommend RADIUS for this job. I would be willing to give some > informal quidance to those interested in doing the actual work... I'm *very* interested in this. We are embarking here on an ambitious project to centralize accounting and billing information with user authentication and access control. We need something scalable beyond 100,000 users, yet still be accessible through secure channels on a nation-wide network. We are already using RADIUS for dialup authentication on our Livingston PM-2e termservers. Luckily, I'm not directly involved in the coding of that project ;-), but if you have any thoughts on alternatives to the traditional UNIX passwd/NIS-based solutions, I'm all ears. -- Brian Tao (BT300, taob@io.org) Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"