From owner-freebsd-security  Sun Apr 19 19:42:59 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA16971
          for freebsd-security-outgoing; Sun, 19 Apr 1998 19:42:59 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16863
          for <freebsd-security@FreeBSD.ORG>; Mon, 20 Apr 1998 02:42:42 GMT
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA03632;
	Sun, 19 Apr 1998 19:42:24 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Wes Peters <softweyr@xmission.com>
cc: Penisoara Adrian <ady@warpnet.ro>, freebsd-security@FreeBSD.ORG
Subject: Re: Using MD5 insted of DES for passwd ecnryption 
In-reply-to: Your message of "Sun, 19 Apr 1998 20:37:02 MDT."
             <353AB4CD.81FEC9DB@xmission.com> 
Date: Sun, 19 Apr 1998 19:42:24 -0700
Message-ID: <3628.893040144@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk

> What do you do when passwd.conf specifies and encryption format you don't
> have installed?  Can FreeBSD programs fail gracefull to bind to a shared
> library?  I've never probed *that* deeply into shared libraries.  :^)

Sure.  Man dlopen(3).  Something which just selectively bound to
either libm5crypt or libdescrypt or libfoocrypt based on the request
would be kind of neat.  It might solve problems elsewhere as well in
terms of eliminating some of the existing symlink hackfixes..

					Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message