-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 16 September 2003 06:08 pm, Jeremy Kister wrote: > while the patches above are not the perfect solution, they are as close as > you can get while Verisign is in power. > > if anyone knows of a patch for BINDv9, please let me know. >
There's a list of all known patches here: http://www.imperialviolet.org/dnsfix.html Also, ISC has stated they're working on a generic patch to resolve the issue in all versions of BIND; assuming they do that, and assuming it stays in the source tree for future versions (and they maintain it when VeriSign starts changing/round robining the IP) that would be the ideal solution. Although someone made a comment about VeriSign complaining that patched versions of BIND would be a "violation of Internet standard protocols" - when I stopped laughing, it occurred to me that hypocritical or no, that could mean trouble for ISC if VeriSign chose to push the issue. - -- Matt Beland [EMAIL PROTECTED] http://www.rearviewmirror.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/Z9WwkgeEps3gMj4RAkArAJ4/ju5kKR1E/ZJYEH5/hUiEHORsqwCfQcbE jDUSorEQKS3TAPtpj1ggD88= =540B -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
