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.

Sign up for GitHub

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

Jump to bottom

CERT_UNTRUSTED errors when using https #105

Closed
evanlucas opened this issue Dec 8, 2014 · 4 comments
Closed

CERT_UNTRUSTED errors when using https #105

evanlucas opened this issue Dec 8, 2014 · 4 comments
Assignees
@indutny
Labels
crypto Issues and PRs related to the crypto subsystem.

Comments

@evanlucas
Copy link
Contributor

I noticed when trying to use npm. This is the error I kept getting

Error: Hostname/IP doesn't match certificate's altnames: "Host: registry.npmjs.org. is not in the cert's altnames: DNS:npmjs.orgDNS:registry.npmjs.orgDNS:www.npmjs.org"

looks to be a missing comma

/cc @indutny
@caineio
Copy link

caineio commented Dec 8, 2014

Hello!

I am pleased to see your valuable contribution to this project. Would you
please mind answering a couple of questions to help me classify this submission
and/or gather required information for the core team members?

Questions:

  1. Issue-only Does this issue happen in core, or in some user-space
    module from npm or other source? Please ensure that the test case
    that reproduces this problem is not using any external dependencies.
    If the error is not reproducible with just core modules - it is most
    likely not a io.js problem. Expected: yes
  2. Which part of core do you think it might be related to?
    One of: tls, crypto, buffer, http, https, assert, util, streams, smalloc, cluster, child_process, dgram, c++, docs, other (label)
  3. Which versions of io.js do you think are affected by this?
    One of: v0.10, v0.12, v1.0.0 (label)

Please provide the answers in an ordered list like this:

  1. Answer for the first question
  2. Answer for the second question
  3. ...

Note that I am just a bot with a limited human-reply parsing abilities,
so please be very careful with numbers and don't skip the questions!

In case of success I will say: ...summoning the core team devs!.

In case of validation problem I will say: Sorry, but something is not right here:.

Truly yours,
Caine.

Responsibilities

  1. indutny: crypto, tls, https, child_process, c++
  2. trevnorris: buffer, http, https, smalloc
  3. bnoordhuis: http, cluster, child_process, dgram

@evanlucas
Copy link
Contributor Author

  1. yes
  2. crypto
  3. v0.12

@caineio
Copy link

caineio commented Dec 8, 2014

...summoning the core team devs!

@caineio caineio added crypto Issues and PRs related to the crypto subsystem. v0.12 and removed need info labels Dec 8, 2014
This was referenced Dec 8, 2014
Closed
Closed
indutny added a commit to indutny/io.js that referenced this issue Dec 8, 2014
@indutny
crypto: separate altname extensions with ", "
12b5e56 
In newly introduced `SafeX509ExtPrint` I forgot to insert separators
between extensions, which lead to the "DNS:...DNS:..." thing for npm.

Fix nodejs#105
@indutny indutny mentioned this issue Dec 8, 2014
Closed
@piscisaureus piscisaureus added the wip Issues and PRs that are still a work in progress. label Dec 8, 2014
@indutny
Copy link
Member

indutny commented Dec 8, 2014

Should be fixed by #113

indutny added a commit that referenced this issue Dec 10, 2014
@indutny
crypto: separate altname extensions with ", "
687dfc9 
In newly introduced `SafeX509ExtPrint` I forgot to insert separators
between extensions, which lead to the "DNS:...DNS:..." thing for npm.

Fix: #105
Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: https://github.com/iojs/io.js/pull/113.patch
@piscisaureus piscisaureus removed the wip Issues and PRs that are still a work in progress. label Dec 13, 2014
@zaheerehmad zaheerehmad mentioned this issue Jul 4, 2017
Closed
@wmertens wmertens mentioned this issue Jun 19, 2020
Closed
@snyk-bot snyk-bot mentioned this issue Apr 24, 2023
Open
@jesec jesec mentioned this issue Jul 4, 2023
Closed
This was referenced Jul 6, 2023
Open
Open
Merged
Open
Open
Open
Open
Open
This was referenced Jul 7, 2023
Open
Open
Open
Open
Open
Open
Open
Open
@dewaynesmith3711 dewaynesmith3711 mentioned this issue Nov 30, 2023
Open
@ZRDK ZRDK mentioned this issue Nov 30, 2023
Open
@karencapiiro karencapiiro mentioned this issue Nov 30, 2023
Open
@BryanLaura BryanLaura mentioned this issue Nov 30, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@indutny indutny

Labels
crypto Issues and PRs related to the crypto subsystem.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@piscisaureus @indutny @evanlucas @caineio