Re: RIPEMD-160
From: Kris Kennaway (kris@obsecurity.org)
Date: 02/23/01
- Next message: Wes Peters: "Re: Bind vulnerability"
- Previous message: Rob Simmons: "RIPEMD-160"
- In reply to: Rob Simmons: "RIPEMD-160"
- Next in thread: Rob Simmons: "Re: RIPEMD-160"
- Reply: Rob Simmons: "Re: RIPEMD-160"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 22 Feb 2001 20:35:26 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Rob Simmons <rsimmons@wlcg.com>
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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- application/pgp-signature attachment: stored
- Next message: Wes Peters: "Re: Bind vulnerability"
- Previous message: Rob Simmons: "RIPEMD-160"
- In reply to: Rob Simmons: "RIPEMD-160"
- Next in thread: Rob Simmons: "Re: RIPEMD-160"
- Reply: Rob Simmons: "Re: RIPEMD-160"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]