On Thu, 22 Jan 2015, Leith Bade wrote:

We use libcurl in this project so I followed on from Daniel's earlier work (http://daniel.haxx.se/blog/2014/08/05/libressl-vs-boringssl-for-curl/) to add support for BoringSSL.

Thanks for your work!

You'll see that I modified your patch slightly to make it smaller and use the #define to empty-macros approach just to avoid #ifdefs within code a little more.

BoringSSL has an incompatible DES API with missing functions. It doesn't seem to have the MD4 functions and it lacks PCKS12 support.

With two additional commits I made curl build and link fine with BoringSSL, as-is.

* Look at how best to print/report BoringSSL version
- BoringSSL does not have "versions", I have been using git commit hashes to track BoringSSL versions in our project

If they don't have any identifiers upstream then I don't think we can just invent something. It may of course be a subtle signal about how sensible it is to base something on this...

* Integrate BoringSSL detection into configure.ac and correctly handle
the missing openssl/ui.h and openssl/engine.h headers (and set the
relevant #defines)

I took a shot at it and it now says "BoringSSL" in the configure summary.

--

 / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to