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.
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...