On Thu, 23 Jun 2005 14:33, Joey Hess wrote: > Note that CAN-2005-2024 has been assigned to this vulnerability.
I've got a couple hours now to look into it. From what I've read, the version I have uploaded is supposed to fix it but testing shows it does not. I'm now looking around to find what I've missed (presumably a patch). Corrin
