[<prev] [next>] [day] [month] [year] [list]
Message-ID: <5.2.1.1.0.20030925111906.075b3e28@blizzard.bluegravity.com>
Date: Thu, 25 Sep 2003 11:20:53 -0400
From: "Timothy J. Biggs" <tjb@...egravity.com>
To: bugtraq@...urityfocus.com
Subject: Re: Privacy leak in VeriSign's SiteFinder service #2
They did setup a mail server for the wild card tld. You send that mail you
suggested and they get your to and from out of it then disconnect you.
--tim
nslookup -type=MX sdfsgggdfasfasdf.com
Server: ns1.bluegravity.com
Address: 64.57.64.2
com
origin = a.gtld-servers.net
mail addr = nstld.verisign-grs.com
serial = 2003092500
refresh = 1800 (30M)
retry = 900 (15M)
expire = 604800 (1W)
minimum ttl = 86400 (1D)
At 05:37 AM 9/25/2003, you wrote:
>On Wed, 24 Sep 2003, Marco Ivaldi wrote:
>
> > What if Verisign is planning to open more similar TCP/IP services on that
> > host? What if they're going to further modify the existing ones, to better
> > invade individuals' privacy?
>
>Up to now, e-mails addressed to misspelled mail domains will not be sent
>to Verisign's Fake-SMTP-service as MX records are used for mail-domain
>resolving. Verisign did not set up wildcard MX records.
>
>However, if you configure your E-Mail-Program or local
>Mail-Transfer-Agent and misspell the hostname of the SMTP-Server for
>outgoing mail, all outgoing mail will be sent to their Fake-SMTP service.
>
>What if Versign is planning to add wildcard MX records as well, so that
>any mail addressed to mistyped/non-existant mail domains like
>"foobar@...sgggdfasfasdf.com" will be sent to their fake SMTP service?
>
>Expect the worst!
>
>hepp...
> Henning
>
>--
Timothy J. Biggs
--
CIO / Senior Vice President
BLUE GRAVITY COMMUNICATIONS, INC.
3495 Haddonfield Rd. Suite 6
Pennsauken, NJ 08109
Toll Free: 1-877-8 HOSTING
Tel:(856)662-9100, Fax:(856) 662-9101
Email: tim@...egravity.com
WWW: www.bluegravity.com
Customer login: http://www.bluegravity.com/login
Powered by blists - more mailing lists