Date: Fri, 15 Nov 1996 14:56:18 -1000 (GMT+10) From: Justin Harvey <jbh@netpci.com> To: Michael Dillon <michael@memra.com> Cc: Gary Palmer <gpalmer@freebsd.org>, freebsd-isp@freebsd.org Subject: Re: Stupid question no 10101 Message-ID: <Pine.BSF.3.91.961115145434.23937D-100000@delenn.netpci.com> In-Reply-To: <Pine.BSI.3.93.961114184743.25227F-100000@sidhe.memra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Or, yet another alternative is to use NIS, I know you said it was insecure but you need to define 'insecue'. I bet it would be more secure than whatever kind of password exchanging mechanism you're thining of programming. NIS isn't exactly 'insecure', IMO I think it's had a bad rap due to people misconfiguring it. You can also configure NIS to share files that are not defaulted with the package. Justin On Thu, 14 Nov 1996, Michael Dillon wrote: > On Thu, 14 Nov 1996, Gary Palmer wrote: > > > If you're an ISP, and need to share password info between machines, > > but not keep identical info on the machines, how do you handle it? NIS > > I think the best way is to have two machines with complete password info > and run RADIUSD on them. Then use hacked versions of login, ftpd, popper > etc. on the other machines to authenticate via RADIUS. On shell account > machines, hack login to add the user to the local passwd database for the > duration of their session and hack getty to yank them out again when they > log off or get disconnected. > > People have created some of this stuff already and one Linux based ISP may > have all of this running but he is still tinkering and won't release any > of it yet. > > Michael Dillon - ISP & Internet Consulting > Memra Software Inc. - Fax: +1-604-546-3049 > http://www.memra.com - E-mail: michael@memra.com > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.961115145434.23937D-100000>