Superfish support for ssl-known-key?

[David Fifield <david () bamsoftware com>]

There's this story about how lots of computers have a trusted root CA
with a known private key.

http://arstechnica.com/security/2015/02/lenovo-pcs-ship-with-man-in-the-middle-adware-that-breaks-https-connections/

It seems like the kind of thing we should detect in ssl-known-key.nse.

http://nmap.org/nsedoc/scripts/ssl-known-key

However, if I understand correctly, we have to change ssl-known-key a
bit for it to work. Superfish will be the issuer certificate, not a leaf
certificate. It means we want to check every certificate in the chain,
not only the leaf.

Robert Graham says this is the key:

http://blog.erratasec.com/2015/02/extracting-superfish-certificate.html
https://github.com/robertdavidgraham/pemcrack/blob/master/test.pem

If so, then this is its fingerprint:

$ openssl x509 -noout -fingerprint -in test.pem
SHA1 Fingerprint=C8:64:48:48:69:D4:1D:2B:0D:32:31:9C:5A:62:F9:31:5A:AF:2C:BD

David Fifield
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/