From owner-freebsd-questions Wed Feb 28 6: 2:57 2001 Delivered-To: freebsd-questions@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 8371737B718 for ; Wed, 28 Feb 2001 06:02:52 -0800 (PST) (envelope-from roman@harmonic.co.il) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id QAA05531; Wed, 28 Feb 2001 16:00:20 +0200 To: "Brandon D. Valentine" Subject: Re: NIS/YP problems on FBSD 4.2-STABLE Message-ID: <983368820.3a9d047476306@webmail.harmonic.co.il> Date: Wed, 28 Feb 2001 16:00:20 +0200 (IST) From: Roman Shterenzon Cc: freebsd-questions@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting "Brandon D. Valentine" : > On Tue, 27 Feb 2001, Brooks Davis wrote: > > >On Tue, Feb 27, 2001 at 09:50:48PM +0100, O. Hartmann wrote: > >> Well, I'm sorry bothering you again with these problems, > >> but they become serious to me, sorry. > >> > >> My intention was to build up a NIS/YP domain. But it seems > >> to be very complex. > > Not to be captious, but it has been my experience that open source > and/or free NIS/YP implementations are not exactly up to scrub. Most of > them work, to a certain extent, and that seems to be enough. This holds > true for all of the BSDs and linux. They tend to work well enough for > basic map sharing, and sometimes only to certain other OSes. When you > look for things like remote modification of account information, things > can start to break down. The code in FreeBSD probably works better than > the rest of them, but even it falls down on some of the higher > functionality of NIS. I genuinely wish I, or somebody better > qualified had the time to write a flexible, extensible, BSD > licensed YP implementation. I think trhat what's missing in FreeBSD NIS implementation is the ability to change password field to "x" for requests from high ports (the present implementation just denies access). I was looking into bringing this to FreeBSD (from linux), but unfortunately didn't quite have time to get to it. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message