From owner-freebsd-isp Mon Mar 15 10:25:46 1999 Delivered-To: freebsd-isp@freebsd.org Received: from carme.eclipse.net.uk (carme.eclipse.net.uk [195.188.32.33]) by hub.freebsd.org (Postfix) with ESMTP id F3B65154D0 for ; Mon, 15 Mar 1999 10:24:44 -0800 (PST) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by carme.eclipse.net.uk (8.9.3/8.9.3) with ESMTP id SAA50732; Mon, 15 Mar 1999 18:23:42 GMT X-Envelope-To: freebsd-isp@freebsd.org Message-ID: <36ED50A6.F11E5C6D@eclipse.net.uk> Date: Mon, 15 Mar 1999 18:25:42 +0000 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en-GB MIME-Version: 1.0 To: Mark Turner Cc: freebsd-isp@freebsd.org Subject: Re: tac_plus config References: <199903151804.MAA00339@tiberius.emperor.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm having ton's of problems getting the ports version > of tac_plus to authenticate for a Cisco AS5300. > I can get it to work but I don't want have to add every > user to the config file. > I just need ppp dialup, and I'd like it to resolve > via /etc/passwd. Anyone have a working example? I haven't tried tac_plus but recently I was helping someone get Radiator (www.open.com.au's radius server) working on BSDI - Radiator's normal method of doing UNIX auth is to look directly into /etc/passwd and do the crypting itself rather than use the system calls to check the password (of course this is oblivious to shadow passwords and MD5). In Radiator there is an option to set to use system calls instead (they do things the way they do so they can cache passwd file access, but it's not going to matter too much with freebsd anyway as it's a database). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message