I assume the security team are already working on this but cant hurt to ask: http://www.net-security.org/secworld.php?id=5366 Regards Steve ===============================================This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.
At 10:50 AM 7/25/2007, Steven Hartland wrote:>I assume the security team are already working on this butThere was a posting on the security list already about it. http://lists.freebsd.org/pipermail/freebsd-security/2007-July/004411.html ---Mike>cant hurt to ask: >http://www.net-security.org/secworld.php?id=5366 > > Regards > Steve > >===============================================>This e.mail is private and confidential between Multiplay (UK) Ltd. >and the person or entity to whom it is addressed. In the event of >misdirection, the recipient is prohibited from using, copying, >printing or otherwise disseminating it or any information contained in it. >In the event of misdirection, illegible or incomplete transmission >please telephone +44 845 868 1337 >or return the E.mail to postmaster@multiplay.co.uk. > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Steven Hartland wrote:> I assume the security team are already working on this but > cant hurt to ask:Before you ask questions on a public list it's generally considered polite to do a little checking yourself, especially in an open source project. As Mike pointed out, the secteam had already addressed this issue on -security, and I had already followed up in detail regarding the upgrade plans. In addition, at the time you posted the updates had all been done in the ports, HEAD (-current), and RELENG_[56] (5 and 6-stable). In any case, it's good that you're on top of your security announcements, and I'm glad to say that this time anyway we're one step ahead. :) Doug -- This .signature sanitized for your protection