3 ms·
The source code to the fixed versions is still available in those cases, and there's essentially no chance that even verbatim copies of the patches for most sec
by cxr 3y ago
The source code to the fixed versions is still available in those cases, and there's essentially no chance that even verbatim copies of the patches for most security fixes would pass the threshold of creativity to be copyrightable. Worst case scenario, you have to work with another person to have them study the fixes that upstream publishes and then explain the vulnerability to you so you can write a fix of your own.
- ezekg 3y agoSo essentially you pay your engineers to maintain a fork, so you can use the software for "free." Then the question of "build vs buy" eventually arises, because maintaining a fork is a costly maintenance burden, and is essentially the "build" side of that question. Seems like the license would be working as intended then. ;) Besides, this assumes you're creating a competing work. Most use cases of FSL can self-host the latest code. That's the whole point.