Date: Sat, 29 Dec 2007 14:17:27 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Garrett Cooper <youshi10@u.washington.edu> Cc: hackers@freebsd.org Subject: Re: BSD license compatible hash algorithm? Message-ID: <20071229031727.GX40785@server.vk2pj.dyndns.org> In-Reply-To: <1896C9EB-E6B3-4B7D-B354-7DE0774D685C@u.washington.edu> References: <5950EE0C-383D-4D6B-9991-A0DEABD2ADE4@u.washington.edu> <20071228003716.GB48997@lor.one-eyed-alien.net> <B8D4C3C6-B867-4550-9F17-4DC6930D10E2@u.washington.edu> <fl2qiv$qoh$1@ger.gmane.org> <1896C9EB-E6B3-4B7D-B354-7DE0774D685C@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--jRdC2OsRnuV8iIl8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 28, 2007 at 06:32:21PM -0800, Garrett Cooper wrote: >Anyhow, thanks for the ideas I really do appreciate it. Overall, I think I= =20 >will stick with BDB's hash(3) (seems less data collision prone, as was=20 >pointed out earlier, and less of a security risk) as I wasn't aware of the= =20 >NULL argument, no filename 'clause' with dbopen(3). Other option might be the Fowler/Noll/Vo Hash in <sys/fnv_hash.h> --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --jRdC2OsRnuV8iIl8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHdbxH/opHv/APuIcRAtptAKCOxJkK84XypxHokJZ7e03VRNWLJwCgjESk Fey0pFhc0sVAJkcJjcDkX44= =Mf5F -----END PGP SIGNATURE----- --jRdC2OsRnuV8iIl8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071229031727.GX40785>