From owner-freebsd-security Mon Apr 20 01:14:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02109 for freebsd-security-outgoing; Mon, 20 Apr 1998 01:14:54 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02102 for ; Mon, 20 Apr 1998 08:14:47 GMT (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id KAA10452; Mon, 20 Apr 1998 10:14:37 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id KAA09666; Mon, 20 Apr 1998 10:14:25 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804200814.KAA09666@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: Wes Peters , Penisoara Adrian , freebsd-security@FreeBSD.ORG Subject: Re: Using MD5 insted of DES for passwd ecnryption Date: Mon, 20 Apr 1998 10:14:25 +0200 From: Mark Murray Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk "Jordan K. Hubbard" wrote: > > 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.. This will need to work if the binary is statically linked as well. I am not sure if dlopen is up to te task yet. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message