Add an OpenSSL compatibility layer.#22
Merged
ejohnstown merged 1 commit intowolfSSL:masterfrom Sep 3, 2021
Merged
Conversation
haydenroche5
force-pushed
the
compatibility-layer
branch
2 times, most recently
from
c94bed8 to
6e47d45
Compare
haydenroche5
requested review from
julek-wolfssl
and removed request for
cconlon
haydenroche5
force-pushed
the
compatibility-layer
branch
from
093326f to
78cfa21
Compare
Member
|
Let's add in the README, that to run the tests you need to use |
julek-wolfssl
requested changes
Aug 27, 2021
haydenroche5
force-pushed
the
compatibility-layer
branch
from
78cfa21 to
86edf82
Compare
haydenroche5
force-pushed
the
compatibility-layer
branch
from
86edf82 to
e078784
Compare
julek-wolfssl
requested changes
Sep 2, 2021
Prior to this commit, some compatibility layer functions were available in wolfssl-py's FFI bindings but only via the wolfSSL names. For example, `wolfSSLv23_server_method` was available, but not `SSLv23_server_method`. This commit adds support for the OpenSSL names. So, a Python module that uses the OpenSSL names can now be more easily ported to using wolfssl-py. For example, the module pyOpenSSL is a Python wrapper around OpenSSL using FFI, very similar to what we're doing with wolfssl-py. These new bindings in wolfssl-py allow us to plug in our wolfSSL FFI to pyOpenSSL, which in turn allows projects using pyOpenSSL to use wolfSSL under the hood. As a proof of concept, I used wolfssl-py with pyOpenSSL to convert the Python module ndg_httpsclient from OpenSSL to wolfSSL.
haydenroche5
force-pushed
the
compatibility-layer
branch
from
e078784 to
7db065d
Compare
julek-wolfssl
approved these changes
Sep 3, 2021
ejohnstown
approved these changes
Sep 3, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prior to this commit, some compatibility layer functions were available in
wolfssl-py's FFI bindings but only via the wolfSSL names. For example,
wolfSSLv23_server_methodwas available, but notSSLv23_server_method. Thiscommit adds support for the OpenSSL names. So, a Python module that uses the
OpenSSL names can now be more easily ported to using wolfssl-py. For example,
the module pyOpenSSL is a Python wrapper around OpenSSL using FFI, very similar
to what we're doing with wolfssl-py. These new bindings in wolfssl-py allow us
to plug in our wolfSSL FFI to pyOpenSSL, which in turn allows projects using
pyOpenSSL to use wolfSSL under the hood. As a proof of concept, I used
wolfssl-py with pyOpenSSL to convert the Python module ndg_httpsclient from
OpenSSL to wolfSSL.