From owner-freebsd-security Thu Feb 22 20:35:31 2001 Delivered-To: freebsd-security@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 7791E37B401 for ; Thu, 22 Feb 2001 20:35:27 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EBACC66C34; Thu, 22 Feb 2001 20:35:26 -0800 (PST) Date: Thu, 22 Feb 2001 20:35:26 -0800 From: Kris Kennaway To: Rob Simmons Cc: freebsd-security@freebsd.org Subject: Re: RIPEMD-160 Message-ID: <20010222203526.A13606@mollari.cthul.hu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rsimmons@wlcg.com on Thu, Feb 22, 2001 at 11:27:49PM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 22, 2001 at 11:27:49PM -0500, Rob Simmons wrote: > I am interested in changing the libcrypt links to point to RIPEMD-160 > libs. I looked in the source, and I noticed that there are a set of MD > based algorithm libs in src/lib/libmd. Is there a way to get these to > work when libcrypt is linked to them? I tried just linking to the three > files like you would to the DES or MD5 libs, but it failed. Well, it's of course not this simple - you would have to modify the libcrypt code. But IMO there's no justification for doing this - MD5 passwords aren't known to be insecure in any way. Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6leiOWry0BWjoQKURAuBFAKC0332sslUaa2N3zqYLZHiv86XyuACg+CPO GC0C4vBKJdlGretcvRIjdLU= =0TX7 -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message