From owner-freebsd-hackers Wed Jul 12 15:27:05 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA28128 for hackers-outgoing; Wed, 12 Jul 1995 15:27:05 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA28122 for ; Wed, 12 Jul 1995 15:27:01 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id SAA05613; Wed, 12 Jul 1995 18:24:02 -0400 From: A boy and his worm gear Message-Id: <199507122224.SAA05613@skynet.ctr.columbia.edu> Subject: Re: NIS+ To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 12 Jul 1995 18:23:57 -0400 (EDT) Cc: JOHN@gab.unt.edu, hackers@freebsd.org In-Reply-To: <199507121940.OAA17920@brasil.moneng.mei.com> from "Joe Greco" at Jul 12, 95 02:40:42 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2408 Sender: hackers-owner@freebsd.org Precedence: bulk Of all the gin joints in all the world, Joe Greco had to walk into mine and say: > > Any plans to support NIS+? Plans? Sure, we got plenty of 'em. Code? That's another story. > Speaking from secondhand knowledge, "most likely when hell freezes over" - as > when we had asked Sun about NIS+ documentation, we were told that it was a > "propietary protocol". That suprised me, especially as we are a Solaris > source licensee and OEM, but then again this was quite some time ago and this > was around the time NIS+ was introduced. > > ... Joe They're probably worried that someone will put together an implementation of NIS+ that works better than theirs. The NYS project is supposed to be working on an NIS+ implementation (covered by the GNU public virus, unfortunately) but last I checked it was still far from finished. (As an aside, there's a chance that the CTR will be getting its hands on some Solaris 2.x source code before too long -- I got the approvals in order but the agreement hasn't been signed yet -- and since I'm the admin this means I'm going to have to put special effort into not letting my eyes stray into the directories where it'll reside, lest I become 'contaminated' by its many horrors. Grrrr....) That aside, you're all forgetting the fact that we can't even think about NIS+ until we get secure RPC working. The Sun RPC distribution has code in it for secure RPC, but it doesn work as shipped due to lack of DES encryption. I toyed with the idea of trying to bring it up on my test machine not to long ago, but then I got sidetracked with other NIS issues and that work thing that keeps getting in my way while I'm trying to enjoy myself. Which reminds me: Bill Fenner, if you're listening and not totally swamped by other things, I still haven't been able to duplicate the problem you described in PR #510. -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~