3 ms·
> Just because 5.3.3 is maintained by CentOS and Debian doesn't mean that every install of 5.3.3 is maintained. There will be a small percentage of installs tha
by jrochkind1 12y ago
> Just because 5.3.3 is maintained by CentOS and Debian doesn't mean that every install of 5.3.3 is maintained. There will be a small percentage of installs that are from-source.
So is it just me, or is this a total release management failure that there can be multiple different things called "PHP 5.3.3" (or any other version number), which behave differently, some of which have security vulnerabilities and some don't.
If you want to know if you are vulnerable or not, knowing you have "PHP 5.3.3" is not enough -- I'm not even sure how you'd tell if you had a patched version or a non-patched version, other than testing it for vulnerability.
Something seems horribly wrong here, no?
- kalleboo 12y agoThis applies to pretty much every popular package in a modern distro. I'm not running bash 4.1.2 (which was vulnerable to shellshock). I'm running bash-4.1.2-15.el6_5.2 (CentOS/Red Hat's patched version). It's quicker for distros to backport specific security fixes than to test all the compatibility implications of updating the whole package to the latest version.
- ircmaxell 12y ago> Something seems horribly wrong here, no? Yes. The distributions are effectively forking these versions, and keeping the same version numbers. Leading to some REALLY awkward problems: https://github.com/ircmaxell/password_compat/issues/10 https://github.com/ircmaxell/password_compat/issues/10 However, it's a tradeoff. It hurts some, helps others. After all, I'd rather have someone get security fixes than nothing...
- vacri 12y agoIt's not as bad as Ruby in Debian, which has the patch version number in the package name. For a while there, 'ruby1.9.1' was version 1.9.3...