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.
[ Parent
| on HN ]
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.