Seems all upside for this project, since all we're measuring is SHA-1 vs SHA-2 usage, and not actually validating anyone's hostname or expiry dates or trustedness, etc.
Chrome doesn't ship with CACert in its trust store. So the only thing ordinary people will see are a big red strikethrough and a privacy error anyway. For those who choose to add the root cert to their trust store, this will make the site match what I hope is the behavior of Chrome in that situation, which is not to validate the added root by its signature.
Seems all upside for this project, since all we're measuring is SHA-1 vs SHA-2 usage, and not actually validating anyone's hostname or expiry dates or trustedness, etc.
Chrome doesn't ship with CACert in its trust store. So the only thing ordinary people will see are a big red strikethrough and a privacy error anyway. For those who choose to add the root cert to their trust store, this will make the site match what I hope is the behavior of Chrome in that situation, which is not to validate the added root by its signature.
Fixes #74.