Date: Tue, 16 Sep 2003 22:20:31 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: John Polstra <jdp@polstra.com> Cc: cliftonr@lava.net Subject: Re: Any workarounds for Verisign .com/.net highjacking? Message-ID: <20030917022030.GE84494@wombat.localnet> In-Reply-To: <XFMail.20030916172804.jdp@polstra.com> References: <20030916.180417.44250294.imp@bsdimp.com> <XFMail.20030916172804.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--LSp5EJdfMPwZcMS1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * John Polstra <jdp@polstra.com> [030916 21:27]: > True, we could probably do it. I guess we'd have to generate a few > random and unlikely queries, try them, and see if all/most of them > resolve to the same address. Or maybe the to the same small set of > addresses, depending on how determined Verisign is to make this work. "*.net" should work, since they basically added a * A record to .com and =2Enet. =20 > I just _love_ how Verisign doesn't even have a reverse DNS record for > that address. Jerks. root@basement:/usr/src# host 64.94.110.11 11.110.94.64.IN-ADDR.ARPA domain name pointer sitefinder-idn.verisign.com --Mike --LSp5EJdfMPwZcMS1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/Z8TuCczNhKRsh48RApjdAJ9FCnStCB97Dk5Dl1xmwvmO+kqf3ACffjLg DlDs4l2FiHSFG1ExVYxEzpM= =OP+j -----END PGP SIGNATURE----- --LSp5EJdfMPwZcMS1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030917022030.GE84494>