-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small source fix makes using BoringSSL easier #52
Comments
+1 FWIW, it looks like |
I am trying to integrate boringssl with boost asio version 1.10.7. But getting several compilation error as : boost/asio/ssl/impl/context.ipp:208:16: error: member access into incomplete type 'SSL_CTX' (aka 'ssl_ctx_st') boost/asio/ssl/detail/impl/engine.ipp:207:34: error: too many arguments provided to function-like macro invocation |
I'm using BoringSSL with ASIO 1.11. BoringSSL is Google's downstream fork of OpenSSL that removes some of the cruft from OpenSSL while remaining source compatible. I've found three issues with ASIO, but I only really need one source fix (which is openssl-fork-agnostic):
ERR_remove_state was deprecated in favor of ERR_remove_thread_state in OpenSSL 1.0.0 (although it remained for binary compatibility).
https://www.openssl.org/docs/crypto/ERR_remove_state.html
The other two issues are:
CONF_modules_unload
isn't declared or defined in BoringSSL. Config modules aren't supported.SSL_R_SHORT_READ
isn't defined in BoringSSL. Unused error codes have been removed.These last two issues can be handled in my own code with a header prefix:
The text was updated successfully, but these errors were encountered: