On Montag, 8. September 2008, Florian Weimer wrote: > Upstream version 1.3.5 fixed multi-part TXT record support. Please > backport this change. The current behavior breaks SPF and other stuff.
Hi, Florian... naturally I would have rejected this bug report and tagged it "wontfix" because the TXT handling does not appear to be a security-related issue. But as you are a member of the security team I'd be interested if and why you would accept this as a security update (IMHO the only way to get updates into a stable distribution). Users running 1.3.4 are used to that broken TXT behavior. It doesn't appear to be a regression from the 3.1.4-1+etch2 revision compared to the original 3.1.4-1 revision packaged for Etch. So I understand that it's annoying. But Lenny is getting closer so if this is really an issue then users will be able to update to lenny and benefit from the 3.1.7 version there which appears to have it fixed. What do you think? Cheers Christoph
signature.asc
Description: This is a digitally signed message part.
