You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → wolfSSL → build as drop-in replacement of OpenSSL libeay32.dll/ssleay32.dll pair
Is it possible to build PolarSSL as drop-in replacement of OpenSSL libeay32.dll/ssleay32.dll pair?
So I can just replace OpenSSL libeay32.dll/ssleay32.dll pair with same DLL name but with wolfSSL's codebase?
Hi,
wolfSSL embedded SSL does provide an "OpenSSL Compatibility Layer", which maps the most commonly used 300 or so functions from OpenSSL down to the native wolfSSL API. Depending on an application's usage of OpenSSL, it may be possible to do a direct drop-in replacement. This can be enabled when building wolfSSL by using the "--enable-opensslExtra" build option, or by defining OPENSSL_EXTRA when compiling wolfSSL.
The OpenSSL compatibility layer is always expanding as we do more ports into existing OpenSSL applications. Did you try compiling against wolfSSL to see if any errors came up?
Best Regards,
Chris
wolfSSL - Embedded SSL Library → wolfSSL → build as drop-in replacement of OpenSSL libeay32.dll/ssleay32.dll pair
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.016 seconds (89% PHP - 11% DB) with 11 queries