[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <019701c38a07$36a34620$531efea9@stickslinger>
From: nodialtone at comcast.net (Byron Copeland)
Subject: Has Verisign time arrived ?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you build it, they will come.
Cut the crapola... I think you're in denial. Where is there a privacy issue here?
- -- "I always wonder why people choose to support MS and then complain about all of these issues that are known in advance."
> -----Original Message-----
> From: Jonathan A. Zdziarski [mailto:jonathan@...learelephant.com]
> Sent: Friday, October 03, 2003 6:57 PM
> To: Byron Copeland
> Cc: 'Frank Knobbe'; full-disclosure@...ts.netsys.com
> Subject: RE: [Full-Disclosure] Has Verisign time arrived ?
>
> The issue isn't the service itself...the issue is the large number of
> privacy violations combined with Verisign's anti-competitive history
> (http://www.nuclearelephant.com/papers/verisign.html). Is catching a
> type-o really worth the risk of your personal information, passwords,
> session ids, and addresses of the people you email getting out to
> marketing agencies? I think not.
>
> A type of type-o catch is a great idea, and should definitely be
> implemented __as a software solution__ in web browsers...where it
> doesn't affect the entire Internet community, and there is less of a
> privacy risk. Then, any privacy issues you DO have can be easily
> remedied by using a better browser.
>
> Jonathan
>
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Truly sad. I personally liked the service... I'm prone to typoz (did I
> mean typos?) with every sentence I write.
> >
> > - -- "I always wonder why people choose to support MS and then complain
> about all of these issues that are known in advance."
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBP34ID2HZJr/4PEW4EQKN/ACfaFQN1z8P+n17vOj9+vk8ebNbkdsAn0k0
yOU09H0iNQkj9bQyVWP2/Nlx
=BKhj
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists