Just like to bring bug #350964 back to the limelight. Briefly recapping Feb 2, I created the bug report Feb 6, unstable fixed by Thomas Feb 13 DSA 969-1 released Feb 15 I questioned if sarge fixed, Thomas, Joey and Steve respond/discuss.
At the moment it looks like Thomas is suggesting that DSA 969 didn't fix this bug, but did fix another bug, the CVE mentioned in the DSA. I don't know if Thomas is saying this based on the text of the DSA, or if he compared the actual package to the patch he suggested. It would be great to get confirmation that either the DSA did fix this bug, or that another DSA might be needed. Cheers Thomas Wana wrote: > Steve Kemp wrote: > >>On Wed, Feb 15, 2006 at 02:01:51PM +1100, Geoff Crompton wrote: >> >> >> >>>This bug has been closed for unstable (see bug 350964) with the 4.6 >>>upload, but will it be fixed for sarge? >> >> >> Please see DSA-969-1 released two days ago: >> >> http://www.us.debian.org/security/2006/dsa-969 >> >> Sarge is fixed. > > > No, this is about Bug #350964, not Bug #344418 (which is fixed in > Sarge). -- Geoff Crompton Debian System Administrator Strategic Data +61 3 9340 9000 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
