From owner-freebsd-security Mon May 3 12:22:39 1999 Delivered-To: freebsd-security@freebsd.org Received: from brooklyn.slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (Postfix) with ESMTP id 02BD7153CB for ; Mon, 3 May 1999 12:22:33 -0700 (PDT) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id PAA13122; Mon, 3 May 1999 15:25:00 -0400 (EDT) Date: Mon, 3 May 1999 15:25:00 -0400 (EDT) From: andrewr To: David Mazieres Cc: phk@critter.freebsd.dk, peter.jeremy@auss2.alcatel.com.au, adam@homeport.org, freebsd-security@FreeBSD.ORG, provos@openbsd.org Subject: Re: Blowfish/Twofish In-Reply-To: <199905031554.LAA09846@reeducation-labor.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You could easily create an implementation of bcrypt that could not be > used as a block cipher. What exactly is magically blessed about MD5? > MD5's compression function (or MD5 itself) functions perfectly well as > a block cipher in OFB or CFB modes. Is there some directive from the > US government allowing the export of MD5 in source form? Are you suggesting the use of MD5? Im assuming it would be bad to use MD5 because it is much quicker for one to possibly crack users passwords.. -Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message