full-disclosure - Re: Verisign abusing .COM/.NET monopoly, BIND releases new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.BSO.4.51.0309171714450.16428@naughty.monkey.org>
From: jose at monkey.org (Jose Nazario)
Subject: Re: Verisign abusing .COM/.NET monopoly, BIND releases new

a number of options exist to help you remedy this issue:

	- bind 9.2.3rc2 supports "delegation-only", stopping some
	  wildcard implementations from making any difference

if you simply want to stop traffic getting there (they are running a
website and a partially functional MTA on that IP):

	- you can BGP null route this
	  http://www.merit.edu/mail.archives/nanog/msg13715.html

	- cisco's NBAR functionality may be used to detect and block those
	  reply packets from coming in by looking for the response from
	  the nameservers.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121e/121e2/nbar2e.htm

note that this wont stop the query from reaching verisign, it will just
stop you from going to that IP. however, for some enforcing network
privacy concerns, that may be worthwhile.

hope this helps,

___________________________
jose nazario, ph.d.			jose@...key.org
					http://monkey.org/~jose/