Bug 1373542

Summary: rh-nodejs4 bundles openssl
Product: Red Hat Software Collections Reporter: Matthias Runge <mrunge>
Component: rh-nodejs4Assignee: Zuzana Svetlikova <zsvetlik>
Status: CLOSED NOTABUG QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rh-nodejs4CC: hhorak, mrunge, thrcka
Target Milestone: alpha   
Target Release: 2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-08 06:26:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthias Runge 2016-09-06 14:41:49 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Honza Horak 2016-09-08 05:56:44 UTC
This topic showed up on Tuesday's SCLo SIG meeting and I recommend Matthias to report it here. However, I checked quickly the nodejs package and the openssl seems to be removed even from the source, as this comment describes that:

# nodejs bundles openssl, but we use the system version in Fedora
# because openssl contains prohibited code, we remove openssl completely from
# the tarball, using the script in Source100

Matthias, why do you think openssl is bundled in nodejs SCL?

Comment 2 Matthias Runge 2016-09-08 06:22:37 UTC
At first glance, I couldn't find something in the spec to make sure bundled openssl is not linked and distributed[1] and from own experience, you'll need a patch to make node work with rhel7s version of openssl, eg. this here [2]


[1] https://github.com/nodejs/node/tree/v4.x/deps/openssl
[2] http://cbs.centos.org/koji/rpminfo?rpmID=63516

Comment 3 Matthias Runge 2016-09-08 06:26:49 UTC
OK, it looks like I looked at the wrong spec file.

This came up as follow-up question to the request to upgrade node to verrsion 6.