On Tuesday 02 Dec 2003 9:33 pm, Wayne Stallwood wrote:
http://lists.debian.org/debian-security-announce/debian-security-announce-2 003/msg00212.html
Patches available for 2.4.18
2.4.23 and 2.6.0-test6 onwards are unaffected.
Incidently, what are people's policies in terms of rolling out software upgrades on servers? I'm admining several Debian machines in the US, and several more in the UK. Be a pain to get to the UK ones but I can be there within a few hours. The US ones I have to rely on remote hands (who are nice enough people but you never want to rely on such people under any circumstances).
I have a box on the office LAN purely to ensure software stability (named, appropriately, 'stable'), installed only last week to organise software rollouts, plus a development LAN server which was recently "sanitised" with the stable machine's software (Debian stable, plus individual newer version software compiled to /opt). Our current workload involves testing and synchronising our UK servers to our stable machine's software specs before doing so on the US ones, and the new kernel will be another step.
Just wondering what else happens "out in the field", knowing how ALUGers tend to be Debian geezers used to getting moaned at for having an "ancient PHP version" installed or something. Never a good idea to develop policies in-house without some experience from elsewhere IMHO.
Experiences welcomed.
Cheers James