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

Allow setting request's "ciphers" option #1091

Closed
wants to merge 4 commits into from

Conversation

Skehmatics
Copy link

Some corporate proxy setups require the use of very specific TLS cipher lists. This set's request's options.agentOptions.ciphers property to a new node-gyp ciphers property to let the user choose the allowed TLS ciphers.

Skehmatics pushed a commit to Skehmatics/apm that referenced this pull request Jan 18, 2017
These settings get passed to any GET call from request and to node-gyp.
nodejs/node-gyp#1091 needs to be pulled for this to actually work.
Copy link
Member

@bnoordhuis bnoordhuis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should update the options list in lib/node-gyp.js and the README and can you add a regression test or two?

lib/install.js Outdated
@@ -438,6 +438,12 @@ function download (gyp, env, url) {
requestOpts.ca = readCAFile(cafile)
}

// Support for setting specific TLS ciphers
var cipherList = gyp.opts.ciphers
if (cipherList){
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style: space before {

lib/node-gyp.js Outdated
@@ -213,4 +214,3 @@ Object.defineProperty(proto, 'version', {
}
, enumerable: true
})

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accidental change?

Remove accidental edit. Development on windows strikes again!
@rvagg
Copy link
Member

rvagg commented Jun 21, 2019

stale? let us know if you want to pursue still

@rvagg rvagg closed this Jun 21, 2019
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.

4 participants