Re:Distribution packages considered insecure
by dozzie on Monday February 22, 2016 @01:58PM
(#11153324)
> There used to be one Linux, one BSD, and a couple of Windows / DOS. Mac was probably around too
And AIX of several releases. And HP/UX. And SGI Irix. And Solaris + SunOS, again, of several releases (mostly backward compatible, though).
Don't say it was easier then than it is today, barring the young guns constantly breaking their new Node.js packages and Ruby gems.
Re:Distribution packages considered insecure
by snuxoll on Monday February 22, 2016 @03:19PM
(#11153947)
Even then, who cares. Software developers didn't have to explicitly support BSD, if there was a BSD user who cared enough they'd work on getting your package in the ports tree. If there was a Debian or Red Hat user that cared enough they'd make a .deb or .rpm. None of this has changed, what HAS changed is library and application developers deciding to say "screw people using existing releases, I'm only putting bugfixes and security updates in the newest release so anyone still using 1.x and caring about stability can sod off".
I package software I care about, but libraries in particular are notorious for not maintaining any semblance of ABI or API compatibility even between minor releases these days. It's increasingly difficult to support this when I have to rebuild or update multiple applications that depend on a library because they decided to make huge breaking changes in a point release or they won't provide any bugfixes for the major release I'm still on.
Re:Distribution packages considered insecure
by 3pt14159 on Monday February 22, 2016 @02:42PM
(#11153641)
Yeah but everything is online right now and we're moving more and more data that _must_ be secured. Back then you really only cared about a couple of platforms - nobody cared if you could hack some random dudes garage or phone.
Re:Distribution packages considered insecure
by snuxoll on Monday February 22, 2016 @03:16PM
(#11153927)
Nobody is asking you to test your software on a million different platforms, just don't abandon your 1.x users the moment you release 2.x. I am not talking about explicitly supporting XYZ distribution, because package maintainers and software developers are two different groups of people.
Backporting security fixes and replicating interconnected bugs across all the combinations of setups is impossible. Just getting the latest version fixed in all is onerous.
Keep current is my philosophy. It's why I like the Ruby community, the global namespace makes it impossible for libraries to stay behind too long.