From owner-freebsd-stable Sun Mar 24 6:26:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from botbay.net (botbay.net [151.197.159.116]) by hub.freebsd.org (Postfix) with ESMTP id BD5C237B400; Sun, 24 Mar 2002 06:26:35 -0800 (PST) Received: from localhost (wcampbel@localhost) by botbay.net (8.11.6/8.11.6) with ESMTP id g2OEQY054227; Sun, 24 Mar 2002 09:26:34 -0500 (EST) (envelope-from wcampbel@botbay.net) Date: Sun, 24 Mar 2002 09:25:31 -0500 (EST) From: "W. Campbell" To: "Crist J. Clark" Cc: Subject: Re: lib crypt/descrypt/scrypt In-Reply-To: <20020323182336.E48968@blossom.cjclark.org> Message-ID: <20020324092206.Q37036-100000@botbay.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sat, 23 Mar 2002, Crist J. Clark wrote: > On Sat, Mar 23, 2002 at 11:14:47AM -0500, W. Campbell wrote: > > When did a single libcrypt replace the separate libdescrypt and > > libscrypt libraries in -STABLE? > > FreeBSD 4.4-RELEASE i386 Release Notes > . > . > . > libcrypt and libdescrypt have been unified to provide > a configurable password authentication hash library. Both > the md5 and des hash methods are provided unless the des > hash is specifically compiled out. Thanks > > My reason for asking... > > > > I've been having some odd errors[1] when profiling, and finally > > traced it down to a stale libdescrypt.so.2 library remaining in > > /usr/lib. > > > > Is there any harm in removing the descrypt and scrypt libraries, > > Nothing in the FreeBSD system should care. No way to tell if you have > third party software that might care, but it is not likely. ircd can sometimes care, but I recompiled all mine with straight libcrypt. > > and > > can there be something in UPDATING letting others know that these > > libraries changed and may need to be removed? > > This is the first time I've heard of any problems with having the old > ones lying around. This is the first time I had problems and noticed issues with the stale libs. > > [1] > > wcampbel@botbay (Stats): bin/mkpasswd > > /usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Undefined symbol > > "_CurrentRuneLocale" > > What is mkpasswd? ircd's wrapper around crypt(), used to generate encrypted passwords for the conf file. profiling ircd and anything else that has a configure script looking for -ldescrypt prior to -lcrypt causes the same error with stale libraries present. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message