Bug 1402372 - NodeJS segfaults when making TLS requests with multiple certificates
Summary: NodeJS segfaults when making TLS requests with multiple certificates
Keywords:
Status: CLOSED DUPLICATE of bug 1394948
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nodejs
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: NodeJS Packaging SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 12:06 UTC by Chris Northwood
Modified: 2016-12-07 13:20 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-07 13:20:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
NodeJS test case (449 bytes, text/plain)
2016-12-07 12:06 UTC, Chris Northwood 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github nodejs node issues 9015 0 None None None 2016-12-07 12:06:48 UTC

Description Chris Northwood 2016-12-07 12:06:49 UTC 
Created attachment 1229032 [details]
NodeJS test case

Description of problem:

When making a HTTP request to a remote endpoint which requires mutual TLS, then a segfault in NodeJS occurs. This does not in the Nodesource built RPMs, but only in the EPEL version.

Version-Release number of selected component (if applicable):

nodejs-6.9.1-4.el7.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Make a TLS request with multiple certificates specified (see attached poc.js)

Actual results:

Segfault

Expected results:

First certificate that is specified gets used (this is what upstream does)

Additional info:
Comment 1 Tom Hughes 2016-12-07 12:19:06 UTC 
This sounds like it might be the same as https://bugzilla.redhat.com/show_bug.cgi?id=1394948 which was happening (EPEL 7 only) when there was an intermediate certificate in the file with the main certificate.
Comment 2 Chris Northwood 2016-12-07 13:20:44 UTC 

*** This bug has been marked as a duplicate of bug 1394948 ***
Note You need to log in before you can comment on or make changes to this bug.