*BSD News Article 53617


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!usenet.eel.ufl.edu!news.ultranet.com!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!zib-berlin.de!irz401!uriah.heep!not-for-mail
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Switching from libscrypt to libdescrypt
Date: 29 Oct 1995 17:27:27 +0100
Organization: Private FreeBSD site, Dresden.
Lines: 17
Message-ID: <470a1f$mr@uriah.heep.sax.de>
References: <46pcm8$ku1@galaxy.ee.rochester.edu>
NNTP-Posting-Host: uriah.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Manu Iyengar <iyengar@galaxy.ee.rochester.edu> wrote:
>Supposing one installed 2.0.5 with the MD5 version of the crypt
>libraries and then wanted to switch over to the DES libraries. What 
>caveats are involved? Apart from encrypted passwords and suchlike, 
>are there any other "things" to be taken care of? I'll summarize if
>there's enough content. Should this be an FAQ? Thanks.

Well, yes, your password encryption will be less secure then. :-)

Apart from this, watch out for init(8) and ed(1)/red(1): they are the
only binaries that are statically linked against libcrypt, so
replacing the shlib doesn't help for them.
-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)