Currently, as a historical artifact, PerProxy gets the server certificate, checks it with Perspectives, then opens a SSL connection to the server and then verifies the server certificate is what it expected based on the Perspectives check.
A more optimal approach would be to just open the SSL connection to the server and check the actual resulting certificate with Perspectives (and Google and whomever else).
Currently, as a historical artifact, PerProxy gets the server certificate, checks it with Perspectives, then opens a SSL connection to the server and then verifies the server certificate is what it expected based on the Perspectives check.
A more optimal approach would be to just open the SSL connection to the server and check the actual resulting certificate with Perspectives (and Google and whomever else).