|
|
BugTraq
Privacy leak in VeriSign's SiteFinder service Sep 23 2003 09:04PM Richard M. Smith (rms computerbytesman com) (2 replies) Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 06:00PM Mark Coleman (markc uniontown com) (3 replies) Re: Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 07:45PM der Mouse (mouse Rodents Montreal QC CA) (1 replies) Re: Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 08:58PM Jay D. Dyson (jdyson treachery net) Re: Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 07:26PM Hugo van der Kooij (hvdkooij vanderkooij org) Re: Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 07:00PM Marco Ivaldi (raptor 0xdeadbeef info) (2 replies) Re: Privacy leak in VeriSign's SiteFinder service #2 Sep 24 2003 08:05PM Diego Bitencourt Contezini (diego redesul net) |
|
Privacy Statement |
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 (at) sdfsgggdfasfasdf (dot) com [email concealed]" will be sent to their fake SMTP service?
Expect the worst!
hepp...
Henning
--
[ reply ]