News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by Gigachad on Friday November 20, 2026 @01:45AM (#50570999)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by socketcluster on Friday November 20, 2026 @02:22AM (#50571273)
It's insane. I maintain a small open source project with only about 100k downloads per week and in terms of funding, it's crickets for me but I assumed projects like OpenSSL which probably every human being on the planet uses daily would get some 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?

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by avhception on Friday November 20, 2026 @03:03AM (#50571557)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @08:08AM (#50574176)
Plus it would bring literally no benefit to your company .
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by throwaway2037 on Friday November 20, 2026 @03:30AM (#50571776)
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...

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by Datagenerator on Friday November 20, 2026 @04:11AM (#50572094)
Interesting, three years no new Release necessary of SocketCluster? That must be quite stable, congrats!
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by josefx on Friday November 20, 2026 @04:39AM (#50572330)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by throwaway2037 on Friday November 20, 2026 @08:06AM (#50574148)
Historically that was true, but it has improved in the last few years.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by pixl97 on Friday November 20, 2026 @10:06AM (#50575694)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by throooooo on Friday November 20, 2026 @04:51AM (#50572422)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by drcongo on Friday November 20, 2026 @04:40AM (#50572334)
If you're a white supremacist, you can get tens of millions donated to your dotfiles.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by quibono on Friday November 20, 2026 @07:13AM (#50573652)
What's this about?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cesarb on Friday November 20, 2026 @09:28AM (#50575112)
I'm not the parent poster, but I believe it was a reference to https://en.wikipedia.org/wiki/Omarchy#Funding_and_controvers...
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by nopurpose on Friday November 20, 2026 @07:03AM (#50573554)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by k_sze on Friday November 20, 2026 @02:31AM (#50571339)
Honest question: shall free software licenses be changed to force large corporations to sponsor free software projects adequately?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by pbowyer on Friday November 20, 2026 @02:47AM (#50571439)
I certainly think so, but we who think this get shouted down because "It's not Open Source(TM)".
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @08:07AM (#50574159)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by tsimionescu on Friday November 20, 2026 @09:16AM (#50574967)
The FSF would say the exact same. So this point is moot, unless you think Richard Stallman is a corporate shill.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cesarb on Friday November 20, 2026 @09:26AM (#50575077)
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".

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by hobo123 on Friday November 20, 2026 @11:22AM (#50577127)
That's why some prefer calling it "libre software."

Also see LibreOffice.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @11:43AM (#50577572)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by ozgrakkurt on Friday November 20, 2026 @02:51AM (#50571466)
This is backwards imo, it is related to people that chose to build these projects. Everyone might have a different decision on it.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by throwaway2037 on Friday November 20, 2026 @03:42AM (#50571882)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by throwaway7356 on Friday November 20, 2026 @04:52AM (#50572427)
> 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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by saghm on Friday November 20, 2026 @08:52AM (#50574666)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by V__ on Friday November 20, 2026 @09:52AM (#50575470)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by mike_hearn on Friday November 20, 2026 @04:15AM (#50572136)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by aaronmdjones on Friday November 20, 2026 @05:27AM (#50572719)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @08:05AM (#50574141)
It has to be the reasonable costs of distribution. It can't just be an arbitrary fee.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by tsimionescu on Friday November 20, 2026 @09:13AM (#50574932)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @04:57AM (#50572476)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by LytraX on Friday November 20, 2026 @02:47AM (#50571437)
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by mradalbert on Friday November 20, 2026 @03:36AM (#50571831)
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
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by mfru on Friday November 20, 2026 @03:46AM (#50571911)
big tech can spare a few arms and legs, though
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cowlevel on Friday November 20, 2026 @04:59AM (#50572489)
AWS has 90% profit margins and still millions of customers.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by StilesCrisis on Friday November 20, 2026 @08:21AM (#50574279)
https://boringssl.googlesource.com/boringssl/

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

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by coliveira on Friday November 20, 2026 @08:57AM (#50574731)
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?