full-disclosure - Has Verisign time arrived ?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1065221807.28969.8.camel@tantor.nuclearelephant.com>
From: jonathan at nuclearelephant.com (Jonathan A. Zdziarski)
Subject: 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."