From owner-freebsd-security Sun May 2 12:48:55 1999 Delivered-To: freebsd-security@freebsd.org Received: from funky.monkey.org (funky.monkey.org [152.160.231.196]) by hub.freebsd.org (Postfix) with ESMTP id D4612151AA; Sun, 2 May 1999 12:48:53 -0700 (PDT) (envelope-from dugsong@monkey.org) Received: by funky.monkey.org (Postfix, from userid 1001) id 51DCD23DC7; Sun, 2 May 1999 15:48:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by funky.monkey.org (Postfix) with ESMTP id 4230A15CC2; Sun, 2 May 1999 15:48:52 -0400 (EDT) Date: Sun, 2 May 1999 15:48:52 -0400 (EDT) From: Dug Song To: Eivind Eklund Cc: freebsd-security@FreeBSD.ORG Subject: Re: Blowfish/Twofish In-Reply-To: <19990502122142.A289@samurai.com> 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 On Sun, May 02, 1999 at 06:16:47PM +0200, Eivind Eklund wrote: > > The point of this exercise would (IMO, at least) only be OpenBSD > compatibility, where OpenBSD for marketeering reasons has decided to > use Blowfish as part of their hash algorithm. marketeering? read the paper being presented by Niels Provos and David Mazieres at next month's USENIX (FREENIX track), and decide for yourself - "A Future-Adaptable Password Scheme": http://www.citi.umich.edu/u/provos/papers/bcrypt.ps.gz this could be rolled into pam_unix for FreeBSD, perhaps. -d. --- http://www.monkey.org/~dugsong/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message