Re: [keyassure] Opening issue #21: "Need to specify which crypto

[Martin Rex <[e-mail]>]

Martin Rex wrote:
> 
> And there are still a number of TrustAnchors in every Browser that
> carry an md5WithRsaEncryption signature.
> 
> But it's actually worse than that -- VeriSign still has a CA cert
> in service with an md2WithRsaEncryption -- and is still using it
> productively (check https://www.hp.com/).

I'm terribly sorry, I mixed up the (by now long) list of VeriSign
RootCA certs.

The RootCA cert under which the server cert for https://www.hp.com
is "VeriSign Class 3 Public Primary Certification Authority - G2"
and uses sha1WithRsaEncryption.  But it still is an X.509v1 cert.

My Firefox 3.5.13 comes with these three VeriSign RooCA certs
that are X.509v1, use md2WithRsaSignature and valid until 02-Aug-2028:

   "VeriSign Class 1 Public Primary Certification Authority"
   "VeriSign Class 2 Public Primary Certification Authority"
   "VeriSign Class 3 Public Primary Certification Authority"
   

-Martin