From owner-freebsd-hackers Fri Dec 6 11:15:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFF5037B401 for ; Fri, 6 Dec 2002 11:15:11 -0800 (PST) Received: from smtp.distributel.net (cns2.distributel.NET [66.38.181.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D530943ECF for ; Fri, 6 Dec 2002 11:15:10 -0800 (PST) (envelope-from paul@colba.net) Received: from colba.net (nat.MTL.distributel.NET [66.38.181.24]) by smtp.distributel.net (8.12.6/8.12.6) with ESMTP id gB6JF9q5077905 for ; Fri, 6 Dec 2002 14:15:10 -0500 (EST) Message-ID: <3DF0F920.D181C500@colba.net> Date: Fri, 06 Dec 2002 14:23:12 -0500 From: Paul Khavkine X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: nsswitch functionality References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There's been a few discussions in the past about that in the past. I actually looked at starting to write some code but ran into a couple things and also lack of time. I would be happy to donate some time (not much for now) if there woudl be a couple people with the knowledge of the subject to help/answer questions. I would really love to use LDAP instead of NIS. Plus i'm not that good with C (not a big problem). Cheers Paul Robert Watson wrote: > On Fri, 6 Dec 2002, Octavian Hornoiu wrote: > > > I have been doing a lot of research into integrating FreeBSD into my > > company's network recently and we have been converting our servers to > > FreeBSD gradually but one of the hurdles to overcome is the login issue. > > In order to make logins seamless across our network I **MUST** use NT > > logins which means I need winbind functionality to work. > > > > Winbind requires nsswitch to work properly and I know that FreeBSD does > > not support it currently but why is this not a top priority at the > > moment? I would much rather have nsswitch working than some of the > > minor features introduced in 5.0. At least, this is my humble opinion > > and I might be asking too much. Is there a dedicated resource working > > on nsswitch at the current moment or is the project dead? > > Right now there is no active work (that I know of) to complete nsswitch. > It's something I've wanted to see in place for a long time, but I've had > some trouble finding funding to make this happen. Having funding would > provide access to a broader array of hands, and always has a good affect > on motivation. I can find you a contractor if you can find the money -- > otherwise my guess is that the support will gradually trickle in, but that > it's something that will take a look longer than either you or I would > like. Having nsswitch in place is very important for precisely the reason > you identify: it's required to properly integrate with a variet of > directory services in use in the enterprise. FWIW, there's no way it will > happen for 5.0, because we're already in the release candidate series. > However, it could be made to happen within a quarter or two. If anyone is > interested in picking up this task unfunded, we can certainly provide the > technical information and work with them to make it happen, but it's a > non-trivial task. There are some work-arounds, but none of them nearly as > pretty as just having nsswitch support :-). One I know of involves > redistributing directory service data via NIS. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Network Associates Laboratories > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message