On Thu, 20 Mar 2008, Jonathan Schleifer wrote:
This is a very bad idea IMO since it is security relevant. Just port the security patch to 1.0.2, provide updated binaries and release a
I wasn't speaking for the TNF/Security Officer. Likely 4.1 will have full 1.0.2, but I dont see 3.2 release having a full 1.0.2, I may be wrong though :)
~BAS
security advisory so everybody can update to fix this bug before someone even tries to exploit it.