On Mon, 30 Jul 2012, Guenter wrote:
when I was on the release binaries I realized that the metalink support
depends on either OpenSSL or gcrypt/gnutls for the md5/sha1/sha256
calculations ... so seems to me that builds with nss, winssl, darwinssl
currently cant support metalink ...
I disagree. Here's why:
I think it is important to keep the layering clear. libcurl doesn't use
metalink, curl does.
If libmetalink needs a sha256 implementation to work, then I would say that
the added code would much better go there. Wouldn't you agree?
adding APIs for sha1/sha256 would be a benefit I think.
I'm scared of the flood of support and quirks and issues and docs and requests
for further crypto functions that would open. All for "it might be good for".
Through the years I've been very strict in only providing an API that handles
file transfers and I think we need to stick with that. We do the file
transfers, and everything else applications need APIs for need to be handled
by others.
There are a myriad of existing libs for crypto/hash functions...
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
