Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove sha1 chain - should default to system roots #2

Merged
merged 1 commit into from Mar 4, 2015

Conversation

flav
Copy link
Member

@flav flav commented Mar 4, 2015

There are two valid chains to follow for the Nutshell certificate. One is signed by “GeoTrust Global CA” root, and the other is signed by “Equifax Secure Certificate Authority” root. The Equifax chain has a SHA1 signature algorithm within the chain which is now bad practice and has been deprecated. We originally shipped this api code with the “Equifax Secure Certificate Authority” as a hard coded CA which is now broken. This commit removes the hard coded Equifaxt root and relies on the (OS) built in root certificates which should contain the “GeoTrust Global CA” root.

sha2_chain

sha1_chain

There are two valid chains to follow for the Nutshell certificate. One is signed by “RapidSSL SHA256 CA - G3” root, and one is signed by “Equifax Secure Certificate Authority”. The Equifax chain has a SHA1 signature algorithm in the chain. This is now bad practice and has been deprecated, however, we shipped this api with the “Equifax Secure Certificate Authority” as the CA which is breaking installs. This commit removes this second chain and relies on the (OS) built in root certificates which should contain the “RapidSSL SHA256 CA - G3” root.

- https://community.qualys.com/blogs/securitylabs/2014/09/09/sha1-deprecation-what-you-need-to-know
- http://sha1affected.com/
flav added a commit that referenced this pull request Mar 4, 2015
Remove sha1 chain - should default to system roots
@flav flav merged commit 62c8a33 into master Mar 4, 2015
@flav flav deleted the deprecate-sha1-chain branch March 4, 2015 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant