Skip to content
This repository was archived by the owner on Apr 22, 2023. It is now read-only.

Add Go Daddy Class 2 CA - G2 certificate#6013

Closed
trollixx wants to merge 1 commit intonodejs:masterfrom
trollixx:master
Closed

Add Go Daddy Class 2 CA - G2 certificate#6013
trollixx wants to merge 1 commit intonodejs:masterfrom
trollixx:master

Conversation

@trollixx
Copy link
Copy Markdown

@trollixx trollixx commented Aug 8, 2013

We received a new certificate from Go Daddy and it is issued by Go Daddy Root Certificate Authority - G2 which root certificate is not presented in Node.js, so https.request couldn't work properly. This pull request fixes the problem.

Certificate taken from https://certs.godaddy.com/anonymous/repository.pki and also presents in bundle received from Go Daddy after certificate generation.

@Nodejs-Jenkins
Copy link
Copy Markdown

Thank you for contributing this pull request! Here are a few pointers to make sure your submission will be considered for inclusion.

Commit trollixx/node@fe8e6ae89f6b836b394f30989875f3640be4de9b has the following error(s):

  • Commit message must indicate the subsystem this commit changes

The following commiters were not found in the CLA:

  • Oleg Shparber

You can fix all these things without opening another issue.

Please see CONTRIBUTING.md for more information

@trollixx trollixx closed this Aug 8, 2013
@trollixx trollixx reopened this Aug 8, 2013
@bhcleek
Copy link
Copy Markdown

bhcleek commented Nov 7, 2013

+1

@indutny
Copy link
Copy Markdown
Member

indutny commented Nov 7, 2013

Hm... this requires a bit of consideration.

Are you sure that your problems can't be solved y setting a ca option in https.request()/tcp.connect?

@bhcleek
Copy link
Copy Markdown

bhcleek commented Nov 7, 2013

In my case, I'm using a third-party module which ends up calling https.request(), and I have no way to pass a certificate into the module to be used by its https.request() calls. The only viable option that we've found so far is to set NODE_TLS_REJECT_UNAUTHORIZED=0 or to get a new certificate that's rooted by one of the default root certificates trusted by node.

Ideally, I'd like a method by which I could tell node to trust specific certificates in addition to its defaults. I don't mind doing some maintenance to make sure my application trusts certificates that I control, but I'm hesitant to start maintaining my own list of trusted certificates when node is already maintaining a list of trusted root certificates.

Interestingly, the default bundle already include the GoDaddy Class 2 certificate, but its out of date from what Go Daddy currently uses.

@bnoordhuis
Copy link
Copy Markdown
Member

I don't really want to merge this PR because ideally we should be generating the certificate list from Mozilla's CA list. It's something that's been on my TODO list for ages now but I never seem to get around to it.

@TooTallNate
Copy link
Copy Markdown

fwiw in our app, we've monkey patched tls.connect() to always pass in a "ca" array for every TLS connection. A nasty hack, but it works...

@bhcleek
Copy link
Copy Markdown

bhcleek commented Nov 9, 2013

@bnoordhuis I understand your concern. Is there any way I can help you implement generating the certificate list from Mozilla's CA list?

bnoordhuis added a commit to bnoordhuis/node that referenced this pull request Nov 9, 2013
Update the list of root certificates in src/node_root_certs.h with
tools/mk-ca-bundle.pl and update src/node_crypto.cc to make use of
the new format.

Fixes nodejs#6013.
@bnoordhuis
Copy link
Copy Markdown
Member

@bhcleek (and anyone else that's interested) - It would be great if you could test #6489. It updates the root certificate list from the certificate data from Mozilla NSS. Includes the Go Daddy Class 2 CA. :-)

@trollixx
Copy link
Copy Markdown
Author

@bnoordhuis Great, then I am closing this PL in favour of a general solution.

@trollixx trollixx closed this Nov 10, 2013
indutny pushed a commit that referenced this pull request Feb 3, 2014
Update the list of root certificates in src/node_root_certs.h with
tools/mk-ca-bundle.pl and update src/node_crypto.cc to make use of
the new format.

Fixes #6013.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants