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-next>] [day] [month] [year] [list]

Message-ID: <8B32EDC90D8F4E4AB40918883281874D9BE0@pivxwin2k1.secnet.pivx.com>
From: thor at pivx.com (Thor Larholm)
Subject: Verisign abusing .COM/.NET monopoly, BIND releases new

> From: Brian Hatch [mailto:full-disclosure@...kr.org] 
> I hate to muck with a DNS server to fix this problem. 
> And since I prefer DJBDNS, a BIND patch wouldn't do 
> me any good anyway.

At least a BIND patch could be useful for ISP's running BIND or even be
reused in DJBDNS and similar.

> Is it always returning the same IP address, or have 
> any other noticable characteristics?  If so I'd think 
> we could set up a firewall rule to drop all DNS 
> replies that contain the Verisign-be-damned IP address. 
> That'd protect everything, regardless of name server or 
> method of access (using host/nslookup/etc manually.)

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.

Dropping DNS replies would just result in repeated DNS queries, changing
the reply to NXDOMAIN as it originally would have been would be better.

Regards
Thor Larholm
PivX Solutions, LLC - Senior Security Researcher
http://www.pivx.com/larholm/unpatched - Unpatched IE vulnerabilities