Use md5sum if ssl library is not found

[neven@…]

In case ssl library is not found, we could use md5sum executable.

[kpfleming@…]

I'd suggest a third alternative: just grab the md5 computation code from any of the dozens of GPL implementations and put it right into the download handler. I don't see any reason to be dependent on openssl (in fact, that's the only reason I even have openssl on my LFS system at this point), and using the md5sum binary is overkill. The MD5 algorithm is not going to change, and the existing code implementations are stable and bug free (and not very large).

And yes, I'm volunteering to do this if everyone agrees. If so, someone make me the owner of this bug and I'll get a patch made in the next few days (don't need CVS access, I'll just post a patch against CVS HEAD).

[kpfleming@…]

Draft patch to close bug

[neven@…]

Could you move all non-handlers files to src/ (digest.c and md5.c). Although they are closely related to handlers, I think it's much cleaner this way, having only handlers themselves in src/handlers/. Should also make all that Makefiles changes unnecessary?

[kpfleming@…]

After thinking about it overnight I've decided that the best course of action is to create a lib/ subdirectory, that will contain the stuff used by other parts of nALFS. The Makefile in that subdirectory will build lib/lib.a.

This will also make the src/handlers/Makefile.in changes very minimal.

Additionally, I forgot to add some error messages to tell the user when the SSL library does not have the digest type they asked for, or if they asked for something other than MD5 without SSL linked in. Will post a new patch in a few minutes.

[kpfleming@…]

Draft 2 patch

[gerard@…]

[Test ignore, making sure alfs-discuss isn't emailed anymore]

[neven@…]

Commited to CVS.