3 ms·
The trouble is, security fixes (generally) don't get backported to older branches. If older branches are even a thing. Say you're on Foo 1.4.7, and the jump to
by Karellen 3y ago
The trouble is, security fixes (generally) don't get backported to older branches. If older branches are even a thing.
Say you're on Foo 1.4.7, and the jump to Foo 1.5 includes a feature re-org you don't want, and no security fixes. So you hold your version on 1.4.7.
But then a security issue is found, and Foo 1.5.1 is released with a fix. Is the version you have vulnerable? Maybe, depending on where the bug is. Is there a 1.4.8 update to fix it? Maybe not. How would you even get it? Heck, if you've switched off automatic updates, have you even heard about the 1.5.1 release? Are you checking on the release announcements for Foo to find out if there have been any security updates, ever?
OK, maybe you check those things. But do you think J. Random User who saw a post on Reddit that said 1.5 sux0rz and they should stay on 1.4.x is going to? And do you like having botnets? Because that's how you get botnets.
- thwarted 3y agoThe trouble is, security fixes (generally) don't get backported to older branches. Even if the security fixes were backported, it would produce a new version of the older branch, and requires an update in order to actually use it. If the security fix is in an older branch or a newer branch doesn't matter: it still qualifies as an update.
- Karellen 3y agoI thought I covered that in the part about needing to check for updates/release announcements yourself if you've turned automatic updates off?