andrewcoppin at btinternet.com
Sat Nov 17 11:40:32 EST 2007
Thomas DuBuisson wrote:
>> BTW, while I'm here... I sat down and wrote my own MD5 implementation.
> How is the performance on this new MD5 routine?
Ask me *after* I modify it to give the correct answers. ;-)
Interesting question: How do you determine when an implementation of
something as complex as MD5 is actually "correct"? I might get it so it
passes all the tests I've tried, but there's some obscure edge case that
makes it fail. How would you know that? Hmm, in fact... how do I know
the implementation(s) in checking my program *against* are correct?
Oh noes! I'm becoming a paranoid cryptographer! LOL.
> It looks like we have
> gone from just one Haskell MD5 implementation (that I know of) to
> three in a short period of time. This isn't counting the C bindings,
> of coarse.
> Also, I changed the license of my implementation to BSD3 a bit ago, so
> you can use that pretty much as you please.
Yeah, there seem to be a few different MD5 implementations floating
around. As far as I know, mine is unique in that it's 100% Haskell and
requires nothing aside from the libraries shipping with GHC in order to
compile. (E.g., I downloaded somebody else's, and it just wouldn't
compile. It was looking for modules that don't exist.)
More information about the Haskell-Cafe