Hi, [...] Sander> Regarding MD4, I only have a link to RFC1320 for you: Sander> http://www.faqs.org/rfcs/rfc1320.html Sander> Sander> Which contains reference code...
Greg> You want it, then you can do the work :-) (i.e. post a patch) Ok, here it is. It adds the following to apr: include/apr_md4.h passwd/apr_md4.c This is probably not the correct location. It actually should go in apr-util in the crypto department, but anyway. Oh, come to think of it, since there is no apr_md4_encode function, the #includes can probably be cleaned up in apr_md4.c. I also updated the md5 code (removed all tab characters and the reference to UINT4, which really should be an apr_uint32_t instead of a typedef'd unsigned int). Greg> Although... I would ask, "who needs this?" I don't think that MD4 is Greg> generally useful, so I would question its inclusion into APRUTIL. MD5 and Greg> SHA1... those are modern/current and get used. But MD4? I had completely Greg> forgotten about that one until you mentioned it. Well some old code uses md4. And sometimes you just need to stay backwards compatible. Sander
md5_md4.patch
Description: Binary data
