Use OpenSSL (locally installed) instead of BoringSSL?


New Member
Is it possible to use OpenSSL, pick it up during the installation, instead of fetching and compiling BoringSSL?

For BoringSSL, Google states:

"BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.

Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability."



New Member
It seems I'm "boring" you guys here :) Anyway...

boring is actually located in /usr/ports/security/boringssl to be compiled and "make"d, in FreeBSD without any issue. So at least, is it possible to point OpenLiteSpeed's ./ (or 'configure') to use this path that includes an already compiled boringssl? --with-bssl="path" didn't work, the installation script still tries to fetch and compile it.

I'd like to achieve having OpenLiteSpeed run on FreeBSD, just to promote it on World Wide Web. :) Any help would be much appreciated.
Last edited: