From owner-freebsd-stable Fri Aug 9 16:10:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7A4637B400 for ; Fri, 9 Aug 2002 16:10:22 -0700 (PDT) Received: from mail.urchin.com (ns2.quantified.com [63.212.171.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5200F43E6A for ; Fri, 9 Aug 2002 16:10:22 -0700 (PDT) (envelope-from dsilver@urchin.com) Received: from danzig.sd.quantified.net (web.quantified.com [63.212.171.5]) by mail.urchin.com (8.12.1/8.12.1) with ESMTP id g79NC1Vo054935; Fri, 9 Aug 2002 16:11:40 -0701 (PDT) (envelope-from dsilver@urchin.com) Date: Fri, 9 Aug 2002 16:10:13 -0700 (PDT) From: Doug Silver X-Sender: dsilver@danzig.sd.quantified.net To: Yanek Korff Cc: "'freebsd-stable@FreeBSD.ORG'" Subject: RE: NIS fails after upgrade to 4.6 In-Reply-To: <51CC94132526754995E79DCF28C0C34D09BBE1@exchange.cigital.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Filter-Version: 1.7 (mail.urchin.com) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's reversed -- the FBSD box is the client, Solaris is the NIS master, so it's using crypt by default. As for authentication, I can't login (either through ssh or the console). The system is getting the NIS maps, it sees my uid/gid. I can 'su - dsilver', but it doesn't let me in the front door. I have a nearly identical 4.4 box which I've compared this upgraded system to, and nothing seems to work; the 4.4 box even has 'md5' in login.conf -- I just tried changing this on the 4.6 to 'des' & ran cap_mkdb, but still no luck. I just added a local user and that worked properly. I've run out of ideas on this -- anyone have a clue as to why this is happening?? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Doug Silver Network Manager Urchin Software Corp. http://www.urchin.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Thu, 8 Aug 2002, Yanek Korff wrote: > If you're trying to authenticate on the Solaris box, your password in NIS > had better be stored in crypt format -- not MD5, unless you've taken > additional steps on the Solaris box beyond with what I am familiar. If you > want to be able to set your password on the FreeBSD box and have login work > on the solaris box using NIS, ensure your crypt links point to the weaker > ones... There is information in the handbook on this subject: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/nis.html#AEN20965 > > Your original post wasn't completely detailed in what kind of authentication > problems you were having when trying to do what so I've made some assuptions > above. If this is not relevant, consider explaining what "problem with the > authentication aspect" you are having. > > HTH. > > -Yanek. > > > -----Original Message----- > > From: Hanspeter Roth [mailto:hanspeter_roth@hotmail.com] > > Sent: Thursday, August 08, 2002 07:15 > > To: freebsd-stable@FreeBSD.ORG > > Subject: Re: NIS fails after upgrade to 4.6 > > > > > > On Aug 05 at 09:44, Doug Silver spoke: > > > > > After upgrading a 4.4-STABLE machine to 4.6-STABLE, NIS is not > > > working. The NIS master is a solaris box, however nothing else has > > > > Could it have something to do with lib*crypt* links? > > Mine seem to be set anew at last update: > > lrwxr-xr-x 1 root wheel 13 Aug 3 20:32 > > /usr/lib/libcrypt.so -> libcrypt.so.2 > > lrwxr-xr-x 1 root wheel 14 Aug 3 20:38 > > /usr/lib/libcrypto.so -> libcrypto.so.2 > > > > -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message