i agree that keeping php4 is not a good idea. if the decision was up to
me i would have completely switched to php4 a long time ago.
and as i said before, there are customer who would prefer to no pay a
single dime and just say: we're ok with the current solution even if
we're not secure anymore and regarding their site being compromised they
have more of an "we'll cross that bridge when we come to it"-attitude.
the only thing i can do is i'll try to make perfectly clear to my
management and the customers still on that box that very soon there will
be no more security fixes and updates for the technology used by their
website and that they're located on a shared server along with other
websites who are in the same situation. if one of the sites on the
server is compromised we can't gurantee the integrity of their
data/website. after that it's up to them to decide what they really want.
regarding the php4 ebuild i was a little bit surprised that they would
drop the ebuild so soon, after all php4 will still get security fixes
until 2008-08. i was wondering, if they keep mysql-4.0 in portage which
isn't supported anymore since summer 2006, why would they want to drop
php4 so quickly?
Georges Toth wrote:
Not to overlook the fact that PHP is dropping support for PHP4 in
August. Switching distributions to get another half year of support
seems to me like getting a tattoo to fit in with the kids at
highschool. Everyone who wants to run updated software is going to have
to make this move at some point in time.
Absolutely !
I'm not saying that trying to keep running php4 is a good idea :-)
--
[email protected] mailing list
