Re:Non-technical security best-practices for open source pro...
by marcosdumay on Saturday June 05, 2021 @06:01PM
(#27408774)
And there are those two links, that are very good:
Re:Non-technical security best-practices for open source pro...
by dredmorbius on Saturday June 05, 2021 @09:13PM
(#27409857)
"Rusty's Rules for APIs" for those wondering.
(Referenced on p. 40 of Greg K-H's preso.)
Re:Non-technical security best-practices for open source pro...
by ocdtrekkie on Saturday June 05, 2021 @04:43PM
(#27408317)
I feel so many companies, especially of operating systems and web browsers, need to understand point 2.
Re:Non-technical security best-practices for open source pro...
by voidfunc on Saturday June 05, 2021 @10:26PM
(#27410198)
2 has been a huge point of pain for me especially since everyone seems to be afraid to increment their major versions now since they don't want to lose the flexibility to break their API.
Re:Non-technical security best-practices for open source pro...
by cortesoft on Saturday June 05, 2021 @09:09PM
(#27409829)
So does number 2 mean you can't ever change your interface?
Re:Non-technical security best-practices for open source pro...
by voidfunc on Saturday June 05, 2021 @10:27PM
(#27410204)
I think #2 is imprecise in its wording. Break between major versions (though, really, you should only break it for a good reason).
What I am seeing is breaking changes more and more in minor and patch versions, especially since developers are afraid to cut a 1.x so they hide behind the 0.x semantic versioning unstable interface clause.
Re:Non-technical security best-practices for open source pro...
by cortesoft on Sunday June 06, 2021 @01:17AM
(#27410972)
This would also only seem to matter if you release security patches to older major versions... otherwise those same people still wouldn't get security updates.
Re:Non-technical security best-practices for open source pro...
by shkkmo on Saturday June 05, 2021 @11:01PM
(#27410396)
I would say, be aware that major inforface changes mean that you might need to support the previous version with security fixes for a long time or leave non-adopters exposed.
1. Make bug reporting easy with an obvious place to report
2. Do not change interfaces between versions because users will hesitate to upgrade to get security patches.
3. For libraries, maintain security fixes for older versions, provide clear documentation so that users can upgrade to newer versions.
4. For applications, either change slowly or make a compelling case for change.