npm / npm/cli

[QUESTION] Effect of strict-ssl=false is unclear

Open
#3,321 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Awaiting Information Release 7.x
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

strict-ssl is documented as follows:

Whether or not to do SSL key validation when making requests to the registry via https.

The questions that come to mind around this is:

  • Is SSL really meant here, not TLS?
  • Validation of what key against what? Presumably the client's? Is it relevant if not using mutual authentication?
  • What happens if said validation fails?
  • Does disabling this introduce an MITM risk, like curl -k would?
  • When is there a good reason for disabling this? Is it required if you're using a self signed certificate? What if you pass that CA certificate into npm, does it need to be disabled still?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the documented strict-ssl setting and trace how npm handles HTTPS certificate validation. Clarify the SSL/TLS terminology, validation and failure behavior, self-signed CA guidance, and MITM implications, then update the relevant documentation with answers to the listed questions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.