Hi zhanghongge,

wolfSSL actively maintains an OpenSSL compatibility layer for an easy rip-and-replace option. We support all the most common OpenSSL API calls in our compatibility layer and map the OpenSSL calls to internal wolfSSL functions. The best answer I can provide at this time is to just try it, move OpenSSL to a temporary location, put wolfSSL in it's place and change your project to use -lwolfssl instead of -lopenssl.

To get started with wolfSSL please see the following links:
https://www.wolfssl.com/wolfSSL/wolfssl-quickstart.html
https://www.wolfssl.com/wolfSSL/Docs-wo … l-toc.html

For more details on the answer to your question please see this link:
https://www.wolfssl.com/wolfSSL/wolfssl-openssl.html

Let us know if you have any further questions. We're happy to help in any way we can.

Regards,

Kaleb & the wolfSSL Team

Hi rodrigoareis,

Yes wolfSSL has several increases planned, in fact the pull requests have been open for some time we just have to finish reviewing them and getting them merged. They are "want to have" at the moment so the priority on them has been de-escalated. You can see the changes in our github repo for example:

https://github.com/wolfSSL/wolfssl/pulls
Compatibility layer part2
Compatibility layer part3
Compatibility layer another part... etc

Warm Regards,

Kaleb