SHA2 support in intercepted traffic

3 posts, 0 answers
  1. Matthew
    Matthew avatar
    33 posts
    Member since:
    Aug 2008

    Posted 29 Apr Link to this post

    The options for the CertEnroll engine list Hash Algorithm as SHA2 (sha-256 specifically), but when I export the root certificate to the desktop (or trust it), the generated CA self-signed certificate has a signature algorithm of sha1. Is there something I need to do to support SHA 2 intercepted traffic?

  2. Matthew
    Matthew avatar
    33 posts
    Member since:
    Aug 2008

    Posted 29 Apr in reply to Matthew Link to this post

    I see the generated certificates are signed as SHA2. Can the CA be signed as SHA2?
  3. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    408 posts

    Posted 10 May Link to this post

    Hello,

    Sorry about the delayed response.

    Is it possible that the export process actually changes the hash algorithm? When you view the Fiddler CA certificate in the certificate store what  has algorithm does it report?

    Regards,
    Tsviatko Yovtchev
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top