LibreSSL
jfx_bridge
| LibreSSL | jfx_bridge | |
|---|---|---|
| 2 | 2 | |
| 1,317 | 7 | |
| 1.2% | - | |
| 9.6 | 0.0 | |
| 5 days ago | about 1 year ago | |
| C | Python | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LibreSSL
- OpenSSL 1.1.1 End of Life Approaching
-
[gentoo-dev] [News review] LibreSSL support discontinued
On the plus side they have Ed25519, on the negative side we don't have BLAKE2 or X25519, etc.
jfx_bridge
- Python2/3 RPC Bridge
-
OpenSSL 1.1.1 End of Life Approaching
I am stuck with an application written in Python2, where porting it to Python3 is difficult – if it was just the Python language changes it wouldn't be a big issue, but a third party library we heavily rely on decided that Python2->3 would be a good opportunity to completely redesign their API. Getting the application to handle that third party API redesign is a big task and thus far nobody has had the bandwidth/pain-tolerance/etc to undertake it.
But recently we've been finding other libraries we use need to be upgraded for various reasons, but the new versions we need to upgrade to are now Python3-only. Stuck between a rock and a hard place.
Until I discovered https://github.com/justfoxing/jfx_bridge – a Python2-to-3 RPC bridge. So now the Python2 app spawns a Python3 subprocess to host some of its libraries which it accesses over RPC. Ugly as hell but for now the least worst option. My hope is we can gradually transition more and more of the app on to the Python3 side of the bridge, and maybe eventually the Python2 side (and the bridge) can be jettisoned.
Which also led me to discover https://github.com/justfoxing/ghidra_bridge – this Python2 app is nothing to do with Ghidra (it is CPython whereas Ghidra is Jython), but I've been mucking around with Ghidra, and being able to write Python3 to control it is a better experience than Python2. I hate the 2<->3 mental context switching I'm forced into and would like as little of it as possible.
What are some alternatives?
OpenSSL - TLS/SSL and crypto library
ghidra_bridge - Python 3 bridge to Ghidra's Python scripting
mbedTLS - An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
GnuTLS - GnuTLS
libsodium - A modern, portable, easy to use crypto library.
Crypto++ - free C++ class library of cryptographic schemes
Botan - Cryptography Toolkit
GnuPG - Mirror of git://git.gnupg.org/gnupg.git — master branch contains no changes from upstream.
Bcrypt - Modern(-ish) password hashing for your software and your servers
s2n - An implementation of the TLS/SSL protocols
LibTomCrypt - LibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines.
digestpp - C++11 header-only message digest library