full-disclosure - 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: <1063809989.3164.14.camel@tantor.nuclearelephant.com>
From: jonathan at nuclearelephant.com (Jonathan A. Zdziarski)
Subject: Verisign abusing .COM/.NET monopoly, BIND
	releases new

> For now, it is returning the same IP address, but I have no trouble
> imagining Verisign evading DNS filters by changing the A records every
> now and then. Any solution to prevent Verisigns greed should keep this
> in mind.

>From what I understand, BIND's approach is much more sophisticated than
a hardcoded (or configured) IP address.  AFAIK, it looks up the wildcard
TLD ip addresses and uses that to filter...so if the address should
change, it will automatically change BIND's filter settings.