upvote
We have known this since at least heartbleed. The answer was that basically no one funds the project and it had only one developer.

All these trillion dollar tech companies have been leaching off open source for free and never contributed back to the projects they rely on.

reply
Honest question: shall free software licenses be changed to force large corporations to sponsor free software projects adequately?
reply
Many important open source projects have already switched to Business Source License. However, they only switched after they became famous. I have not seen any projects that became famous that started with BSL.
reply
> Many important open source projects have already switched to Business Source License.

No: first not "many", but very few. And second they are proprietary projects.

reply
Some of us have the radical opinion that the definition of open source isn't what a specific organization (with no trademark on the term) dictates, but whether the source is open.

Other people express strong opposition to the idea that "open" might just mean the same thing as "available" in the context of open source. None of those people have proposed a more coherent definition that I've seen of what that word means in that specific phrase though.

reply
"Open Source" and "Free Software" are both well-established terms with well-documented histories of debate and consensus-forming among huge and healthy communities over a span of decades, and organizations that steward the meanings of those terms. Just because you don't like them doesn't mean you get to pretend you're the first person to try to define the word "open" for software.

https://opensource.org/osd https://www.fsf.org/licensing/

reply
I often hear this criticism and "bait-and-switch" is also mentioned. At the same time, when you have a small project or tool only used by a handful of people the risk of it being hacker or not responding in time is very different to a project which is essential to the whole world. I don't now what a realistic solution would look like though.
reply
Then it wouldn't be free software anymore.
reply
Yes, they should do this. Howvee, they'd stop being considered free software and open source.

Alternatively they can put such large share-back requirements that corporations don't want to use it and would rather pay for an alternate license. SSPL and to a lesser extent AGPL achieve this.

reply
A free software license is by definition a license that doesn't place requirements on anyone to pay for it, sponsor it, contribute or otherwise. If a license didn't grant these freedoms, it wouldn't be a free software license.

What you're asking is, should widely used libraries be proprietary software sold for money? And that is indeed an honest question. There's a huge ecosystem of developers out there who say yes, there's nothing special about that idea at all.

For example, on Apple, Google and Microsoft platforms you don't use OpenSSL when writing native apps. You use the vendor's cryptography APIs. The licenses of Windows and macOS force all users large or small to pay for them. On Android, the native crypto provider is Conscrypt:

https://github.com/google/conscrypt/

... which is open source, but you will notice that it doesn't accept outside contributions and is funded by revenue from Android's proprietary components licensing. So that's very close to the model you're suggesting: it's "open source" but in practice large corporations pay Google lots of money for the privilege of shipping it.

Moreover Google fund BoringSSL and other forks of OpenSSL. The issue here isn't funding levels (anymore). The issue is that OpenSSL is written in C, and not very good C at that.

reply
Minor nitpick, but at least as far as the GNU GPL goes, it explicitly allows you to charge for software distribution when the software came bundled with a tangible item (like the firmware of an IoT device). The distributor can require you to pay them to get it. This was more common in the old days when software mostly came on CD-ROMs and you'd be getting another physical item in the mail, but the provision remains in the GPLv3 under section 6(b)(1) as an option that the distributor can require.
reply
It has to be the reasonable costs of distribution. It can't just be an arbitrary fee.
reply
Not exactly. You can charge whatever you like for the software - but whoever buys it from you is then allowed to give it away for free to anyone else, so this is only a theoretical possibility.

The thing you're allowed to charge for but only a reasonable amount is to provide the sources to software you have previously distributed, for free or otherwise. If I get some binaries from you and then request the sources too, under the GPL, you are forced to provide them, but you can ask for a fee to cover the transfer costs.

reply
I certainly think so, but we who think this get shouted down because "It's not Open Source(TM)".
reply
Have you ever wondered who's in charge of choosing what counts as Open Source(TM)? Look no farther: https://opensource.org/sponsors

Yes, that Automattic. Yes, that Google, AWS and Cisco. Yes, that Microsoft. There are one or two entities in this list I don't mind but... damn.

It's time to retire the phrase "open source" and go back to "free software". Not many people know "open source" was originally coined by corporations who didn't want anything to do with freedom.

reply
Not many people seem to know that the definition of "open source" they use (the OSD) is actually the definition of "free software" Debian uses (the DFSG) with the serial numbers filed off.

The problem with "free software" lies exclusively with the English language; other languages don't have the same issue due to having separate words for "freedom" and "zero price".

reply
Debian is free to use any inclusion criteria it wants - especially since it still includes software thst doesn't meet the criteria. It shouldn't become the global default definition of "open source" though.
reply
That's why some prefer calling it "libre software."

Also see LibreOffice.

reply
The FSF would say the exact same. So this point is moot, unless you think Richard Stallman is a corporate shill.
reply
This is backwards imo, it is related to people that chose to build these projects. Everyone might have a different decision on it.
reply
Not allo companies loot OS projects with no contributions. M$ has contributes back to many OS projects and Google has dozens of OS projects themselves.

And when Redis changed their license for such reasons, companies and people united to create ValKey or even the Centos/Rocky linux situation.

reply
Redis cloud would cost you arm and leg compared to self hosting. I gives me an idea why big tech was not keen on making business with them
reply
AWS has 90% profit margins and still millions of customers.
reply
big tech can spare a few arms and legs, though
reply
It's insane. I maintain a small open source project with only about 100k downloads per week and so, in terms of funding, it's crickets for me but I assumed famous projects like OpenSSL would get some decent funding.

Then I read articles about billionaires donating millions or even billions to various (sometimes frivolous) charities and I wonder WTF.

The numbers just don't add up. It's like there is an invisible force field preventing people from donating money to open source?

Crazy to think that the people who once posted a dumb viral 30-second meme video on YouTube probably got more money than the author of a complex, world-famous open source project which has been at the top for decades and which quite literally intermediates every aspect of almost every human's life.

Does not compute.

reply
OpenSSL receives millions of dollars of funding each year. The corporation that runs the foundation reported 5.5M USD funding in 2024[1], and 5.0M USD funding in 2025[2]. These days, OpenSSL is well-funded.

From your HN bio, I guess this is your project: https://socketcluster.io/

From the home page, I see that you are sponsored by two different companies. To me, "in terms of funding, it's crickets for me" isn't an honest statement.

If funding is such a problem for you, why don't you use a non-open source license, e.g., Business Source License? This would allow non-commercial projects to use your software for free, but commercial users need to pay. There are a bunch of big, important open source projects that already changed: HashiCorp, CockroachDB, MariaDB, etc.

[1] https://openssl-corporation.org/blog/2025-02-14-annual-repor...

[2] https://www.openssl-corporation.org/assets/Annual-Report-202...

reply
From my understanding the problem was never that OpenSSL had no money, but that all the money it had was tied to services and features that didn't help improve the libraries overall security and in some cases where even outright harmful.
reply
This is really the same for most enterprise software. Customers pay for features , I guess they think the security is implied, but more features at a rapid pace typically ruins long term security.
reply
Historically that was true, but it has improved in the last few years.
reply
I don't believe BSL = commerical issues have to pay. Typically it means that the code can be used internally, but not distributed or resold as a service.
reply
Interesting, three years no new Release necessary of SocketCluster? That must be quite stable, congrats!
reply
AFAIK donation distribution is still unsolved problem. That is there is no single org business can donate $1M to and have it distributed among all the projects business identified it relies on.
reply
I would very much like for my employer, who benefits massively, to donate. However, the people in charge of the money decisions don't know anything about software and don't want to be lectured by me. They have _important business stuff_ to do. Sigh.
reply
Plus it would bring literally no benefit to your company .
reply
I understand why you would say that, nut it's not even true. We've had plenty of bugreports that have had crippling effects. For a minuscule fraction of these, I have been able to provide fixes or workarounds. But mostly, I would have been thrilled to get paid support there!
reply
[flagged]
reply
What's this about?
reply
I'm not the parent poster, but I believe it was a reference to https://en.wikipedia.org/wiki/Omarchy#Funding_and_controvers...
reply
https://boringssl.googlesource.com/boringssl/

All yours! Use it to your heart's content.

reply
If you think about it, giant corporations are making gobbles of money from people who wrote software for free and in their free time. And they still complain when it doesn't work as they expected. Why they didn't fund a better version of OpenSSL?
reply
If you've ever tried using OpenSSL you'll know that it's true.

The API is a fractal of bad design. Not just that, but because of the API refusing to make sensible choices, it forces everyone using it to be an expert in cryptography, with predictable results for those programs that use it.

reply
How it happened? A lot of features in OpenSSL was written as part of a PhD and dumped in the repo without any thought about long term maintainability or quality. Now, during the last 5 years or so, people have been trying to straighten it out, but this is a pretty daunting task.
reply
A related problem is that the IETF's RFC production center (that's its actual name) is manufacturing new RFCs far beyond the capability of anyone to keep up, and every half-assed idea anyone ever has or that some vendor pays an IETF consultant to turn into an RFC for them ends up getting bolted onto OpenSSL, which serves as the AB-positive universal recipient that everyone tests their ideas on, typically in a half-finished, barely-tested form of which Heartbleed was the prime example. It's not even a Red Queen problem because no matter how hard you run you're still falling behind each time.
reply
SSL/TLS has always been a wonky and complicated standard built upon other wonky standards like x509 and ASN.1 (for PKI) that nobody would touch unless they are forced to.

There is a reason why people did not do a lot of TLS (outside of anything involving monetary transactions) before Firesheep, the NSA leaks were the final nail in the coffin for unencrypted HTTP. On top of that Let's Encrypt and ACME did not exist, so TLS was behind a paywall on top of that.

And then everything proliferated relatively quick even for tech standards. I guess people grabbed onto the next available tooling just like a drowning person would take any piece of driftwood.

Not so fun fact: AFAIK the openssl binary was initially explicitly meant to be only used for testing. That is why its command line is so strange. It was initially meant to expose a couple of low-level primitives, not to implement workflows. One example would be the openssl-ca man page, which explicitly mentions this. People didn't care because unfortunately you could somehow do everything you could ever want with the openssl binary and I guess that is also something how the impression stuck that openssl is the most advanced library.

reply
> Not so fun fact: AFAIK the openssl binary was initially explicitly meant to be only used for testing.

I'm in shock ! Someone noticed ! Thanks man ! :)

In the meantime in real world IT :>>

line 57: https://github.com/acmesh-official/acme.sh/blob/master/acme....

line 306: "This script requires openssl binary" https://github.com/dehydrated-io/dehydrated/blob/master/dehy...

Pretty recommended scripts :)

And I'm sure there are more and not only for ACME, for example I'm sure I saw few examples in production setup docs from IBM and Redhat... :>

Yes, openssl library is wholesale backdoor, subtype: footgun.

reply
Many people are using forks that are mostly API compatible. So the ubiquity is not as huge a problem as it used to be.
reply

    > And yet, as an open source developer myself, I know how little people care about code quality.
This is a weird statement. I am someone who has worked on closed-source internal enterprise software for my entire career. Universally, the internal source is worse that the numerous open source libraries that we use. If anything, open source has "more eyeballs" than closed source, so the code quality will be better.
reply
I don’t know. If you are using all the tools at your disposal like linting, static analysis, dynamic analysis, DAST (if web), fuzzing, SCA, etc and correcting your code for the findings, dispositioning and correcting them can that really be said? Open source doesn’t always
reply
I'd like to point you to: https://www.haproxy.com/blog/state-of-ssl-stacks

Among the deeply technical and highly credible and detailed articles I've read in my life, it's definitely the spiciest. At the end:

> It is often said that fixing a problem requires smarter minds than those who created that problem. When the problem was architected by a team with strong convictions about the solution‘s correctness, it seems extremely unlikely that the resolution will come from the team that created that problem in the first place. The lack of progress in the latest releases tends to confirm these unfortunate hypotheses. The only path forward seems to be for the team to revert some of the major changes that plague the 3.x versions, but discussions suggest that this is out of the equation for them.

IOW this extremely strong claim does seem to be supported by extremely credible actors.

reply
Google forked OpenSSL in 2014 (BoringSSL) with a pretty similar rationale, stated more diplomatically.
reply
I just wanted to check what became of the original LibreSSL fork. Google forked it into Boring SSL, that's what happened.
reply
If you use OpenBSD that's what you get in the base system.
reply
I remember a long time ago reading openssl was dumpster file code quality wise. I guess it was just built that way and never improved.
reply
I wanted to see how OpenSSL handles the x64 instructions to accelerate SHA1 hashing and it turns out the assembly code is generated by a perl script.
reply
That's normal, if outdated - you'd use Python in anything written since 2010
reply
That's not automatically bad, in fact it can be better than just inlining the instructions. I won't judge this instance of the pattern, but if faced with (perhaps incomplete at the time) intrinsics, or hand coded inline assembly, vs generating with an external script (or "mini compiler" if you will), it might be less error prone to generate.
reply
Assuming you mean x86, that part was originally written around 30 years ago via this funky setup that did MD5 and SHA-1 from the same code. It's not really any kind of example of current practice.
reply
No, the SHA-NI instructions
reply
> You wonder; how could this happen?

It all came from a bad place. OpenSSL grew from primitives created by cryptographers. Cryptographers are great, and they make fabulous things. But almost none of the understand software development or care a great deal about the mundane matters of API design, or the obnoxious limitations of naively designed processing elements.

Others have cited the documentation for EVP_EncodeBlock(). In the mind of a cryptographer, the text is perfectly clear and trivial, and they likely haven't exposed themselves for many years to anyone that can't read that exactly once and not immediately and correctly visualize the necessary formulae. Nothing wrong here at all. The fact that on real computers, numbers don't just scale to whatever value a computation requires is merely a defect in the design of the machine.

reply
Mathematician: "Um, just ignore that infinity symbol there"
reply
Because you don't roll your own SSL.
reply