You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
macOS has long deprecated OpenSSL in favour of its own crypto framework and does not provide a good amount of backwards compatibility; you actually have to install OpenSSL through homebrew.
On Windows, OpenSSL isn't guaranteed to be installed either...
A lightweight option would be to create a libJumpknots backend for mbedTLS - since it is quite easy to embed and use within your own projects without having to work with a gigantic codebase like OpenSSL.
Do you think this would be a plausible possibility?
The text was updated successfully, but these errors were encountered:
In general, I would say, OpenSSL is still the defacto standard in opensource, as it should be. It's the best option because of its age, community, contributions and scrutiny of its code.
But you're right in saying it's not guaranteed to be installed, applications have to install it alongside itself, which can be a pain. But a lot of projects do and require so anyway.
So I understand the reasoning behind this, but I don't see any other project or library doing anything about this either.
macOS has long deprecated OpenSSL in favour of its own crypto framework and does not provide a good amount of backwards compatibility; you actually have to install OpenSSL through homebrew.
On Windows, OpenSSL isn't guaranteed to be installed either...
A lightweight option would be to create a libJumpknots backend for mbedTLS - since it is quite easy to embed and use within your own projects without having to work with a gigantic codebase like OpenSSL.
Do you think this would be a plausible possibility?
The text was updated successfully, but these errors were encountered: