Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support sha512 digest in CertificatePinner
See original GitHub issueWe have requirement to use sha512 digest for certificate pinning, and we have that in legacy code based on good old TrustManager. We planned to migrate it to okhttp. However the CertificatePinner in okhttp supports sha1 and sha256 only.
On the other hand, CertificatePinner does not have extensibility in mind, so I cannot extend the class for additional type of digest. The simplest way to get out of the situation seems to be enhancing the CertificatePinner directly. If there is no fundamental cause to avoid sha512 digest, i am happy to contribute enhancement to the class.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@hkhc that’s a bad policy and your infosec people should feel bad.
Curious, does this come from an RFC? or a decision made within your org. Generally https://tools.ietf.org/html/rfc7469 seems to assume sha256 is the way forward for now.