From owner-freebsd-current Sun Mar 12 14:22:58 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4B0D037BC18; Sun, 12 Mar 2000 14:22:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 491A52E8156 for ; Sun, 12 Mar 2000 14:22:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 12 Mar 2000 14:22:57 -0800 (PST) From: Kris Kennaway To: freebsd-current@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true doesn't work In-Reply-To: <200003121450.PAA29943@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Mar 2000, Oliver Fromme wrote: > Maybe I'm just too dumb... It's my understanding that the > purpose of the ``NODESCRYPTLINKS'' option in make.conf is > to prevent overwriting the libcrypt symlinks in /usr/lib. > Well, it doesn't work. > > I cvsupped today in the morning (~ 9:00 UTC on Sunday), added > NODESCRYPTLINKS=true to /etc/make.conf, "make buildworld", > "make installworld", and couldn't log in anymore because > the symlinks had been set to libscrypt (and I'm using DES > passwords). > > I guess that's not how it's supposed to work, is it? No :) DES crypt links have a "higher priority" than MD5 crypt links - if you do a make install in secure/lib/libcrypt or lib/libcrypt, each will overwrite the libcrypt links of the other. The difference is that make world runs secure/lib/libcrypt last, so the DES links win. So, as the name suggests, unless you want no DES crypt links (keep the MD5 links, please!), you don't use it. "WANTDESCRYPTLINKS" is the historical behaviour which hasn't changed. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message