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