full-disclosure - PGP vs. certificate from Verisign

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: Windows password security audit tool. GUI, reports in PDF.

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

From: security at brvenik.com (Jason)
Subject: PGP vs. certificate from Verisign

yossarian wrote:
> What I wonder - will Verisign have set up CRL servers yet? Remember the IE
> problem when someone got hold of MS certificates? The MS-fix was
> blacklisting them locally, the real problem was that there was no revocation
> servers. Then again, how many concurrent connections would they get if MS
> sent out a critical update?
> 
> So - stick to PGP - forget about PKI.
IIRC, the problem was not that Verisign could not revoke the keys it was 
that IE had no way of checking the revocation status, It was a MS 
implementation problem not a problem with the issuing authority. This 
has been resolved in IE ( in some places ) and you can now enable the 
revocation checking however it is not enabled by default.

Google provided a good place to brush up on the incident.
http://www.amug.org/~glguerin/opinion/revocation.html


[snip] ...