On 4/14/15, 8:29, "Mark Jeftovic" <mar...@easydns.com> wrote:
>Joke all you want. This is worse than heartbleed. In short and if I understand this correctly, the problem isn't AXFR's existence or use, the problem is that systems are poorly configured. It's like blaming your aorta if a cut causes blood to spill. The problem isn't that there is an aorta, it's the cut. I understand this as a problem. Tools in common use that do not ease management or fail to make it apparent what the user has configured is worthy of CERT advisories (akin to "smoking will kill you" stickers I've seen on cigarette boxes). But blaming a structural element of the protocol isn't the way to address the issue.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
