SaaSHub helps you find the best software and product alternatives Learn more →
Top 20 C Openssl Projects
-
Wow... reading this article in full really made me lose hope in OpenSSL, the project and the library.
I was well aware of the expected inconveniences any new major OpenSSL release would trigger (esp. older, less actively maintained applications having to adapt their API usage to keep working) going in, but what the linked github issue/PR comments hint at is just... mental.
As best illustrated by https://github.com/openssl/openssl/issues/20286#issuecomment... not only seem the core developers not care about runtime performance at all, they also seem to have a completely absurd perception of their own project, esp. in relation to other, genuinely small FOSS projects.
It's just wild. I hope this can still be turned around, and OpenSSL can somehow re-emerge from this clusterfuck as the stable bedrock of web transport security that we learned to rely on from 2014 onwards.
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
libhv
🔥 比libevent/libuv/asio更易用的网络库。A c/c++ network library for developing TCP/UDP/SSL/HTTP/WebSocket/MQTT client/server.
-
wolfssl
The wolfSSL library is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3 and DTLS 1.3!
You may be talking about that, but I'm not. I was talking about the task-specific memory footprint. I didn't say anything at all about the rest of the computer.
And even that wasn't meant to be taken literally. I kind of thought that was obvious[1].
But in the end, OK, you're right. You probably could fit the banking app logic in 64K, but you'd have to rely on the OS to provide things like crypto, the network stack, and the I/O. So the machine as a whole would need more than that to get the job done. And the UI would be pretty bad if you stuffed even the app part into 64k.
No problem fitting it all into megabytes, though. Definitely no need for it to be gigabytes. I challenge you to explain what needs to be there that would make the entire system, OS, app, and all, need even one gigabyte of RAM to run even a very pretty, featureful banking app. Or even a quarter of a gigabyte.
By the way, you can put TLS itself in less than 64k (see for example https://github.com/wolfSSL/wolfssl). But you have to profile it way down, maybe to the point of leaving out X.509, so you don't really have "full on" TLS. On the other hand, a lot of the footprint is because the TLS protocol itself is bloated and overcomplicated, and no, that bloat doesn't improve the security.
[1]: ... and I mean, if we're going to get pedantic like that, nobody can write an SSL implementation with modern ciphers for any computer, because modern ciphers weren't introduced into the protocol until after it was renamed TLS. Actual SSL isn't something anybody should be using now. Even TLS 1.1 isn't.
-
LibreSSL
LibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to [email protected] are welcome.
-
-
-
libuhttpd
A very flexible, lightweight and high performance HTTP server library based on libev and http-parser for Embedded Linux.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
engine
A reference implementation of the Russian GOST crypto algorithms for OpenSSL (by gost-engine)
-
-
-
-
-
-
-
amissl
:closed_lock_with_key: AmiSSL is the AmigaOS/MorphOS/AROS port of OpenSSL. It wraps the full functionality of OpenSSL into a full-fledged Amiga shared library that makes it possible for Amiga applications to use the full OpenSSL API through a standard Amiga shared library interface (e.g. web browsers wanting to support HTTPS, etc.)...
-
-
tls-ca-manage
Multi-level Certificate Authority Management tool, front-end tool to OpenSSL, written in bash shell.
-
webcert
WebCert is a Web application to generate and manage digital certificates in cases where no "full" CA is needed.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
C Openssl discussion
C Openssl related posts
-
The State of SSL Stacks
-
I can't pay rent because devs just don't care
-
OpenSSL 3.5 [LTS] Released
-
Okta Bcrypt incident lessons for designing better APIs
-
The QUIC API OpenSSL will not provide
-
Embedded TLS Library for Applications, Devices, and the Cloud
-
Encryption: ciphers, digests, salt, IV
-
A note from our sponsor - SaaSHub
www.saashub.com | 14 May 2025
Index
What are some of the best open-source Openssl projects in C? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | OpenSSL | 27,331 |
| 2 | libhv | 7,141 |
| 3 | wolfssl | 2,498 |
| 4 | LibreSSL | 1,403 |
| 5 | lagrange | 1,295 |
| 6 | OpenSSL | 964 |
| 7 | libuhttpd | 402 |
| 8 | engine | 399 |
| 9 | oqs-provider | 324 |
| 10 | tls-scan | 310 |
| 11 | openssl-cmake | 288 |
| 12 | openssl | 244 |
| 13 | tpm2-tss-engine | 158 |
| 14 | DTLS-Examples | 143 |
| 15 | amissl | 93 |
| 16 | openssl | 90 |
| 17 | tls-ca-manage | 42 |
| 18 | webcert | 29 |
| 19 | stata-shasum | 7 |
| 20 | quic-echo | 2 |
Sponsored
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com