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

failed test: parallel/test-tls-no-sslv3.js with shared openssl #618

Closed
jbergstroem opened this issue Jan 27, 2015 · 4 comments
Closed

failed test: parallel/test-tls-no-sslv3.js with shared openssl #618

jbergstroem opened this issue Jan 27, 2015 · 4 comments
Labels
tls Issues and PRs related to the tls subsystem.

Comments

@jbergstroem
Copy link
Member

Path: parallel/test-tls-no-sslv3
child_process.js:1100
  var err = this._handle.spawn(options);
                         ^
TypeError: Bad argument
    at TypeError (native)
    at ChildProcess.spawn (child_process.js:1100:26)
    at exports.spawn (child_process.js:959:9)
    at Server.<anonymous> (parallel/test-tls-no-sslv3.js:25:16)
    at Server.g (events.js:184:16)
    at Server.emit (events.js:95:17)
    at net.js:1167:12
    at process._tickCallback (node.js:337:11)
    at Function.Module.runMain (module.js:489:11)
    at startup (node.js:111:16)

The problem is that common.opensslCli will return false instead of a path to the openssl-binary, since it hasn't been built. The simple way is just to check for false before running the test, but it feels like a poor decision since we'd probably want to run the test suite with a shared openssl as much as possible (so the user can verify that their setup is correct).

@micnic micnic added the tls Issues and PRs related to the tls subsystem. label Jan 28, 2015
shigeki pushed a commit to shigeki/node that referenced this issue Feb 9, 2015
When configured with share openssl, use external openssl command and
check if it can be executed.

Fixes: nodejs#618
shigeki pushed a commit to shigeki/node that referenced this issue Feb 9, 2015
When configured with share openssl, use external openssl command and
check if it can be executed.

Fixes: nodejs#618
shigeki pushed a commit that referenced this issue Feb 9, 2015
When configured with share openssl, use external openssl command and
check if it can be executed.

Fixes: #618
PR-URL: #762
Reviewed-By: Ben Noordhuis <[email protected]>
@shigeki
Copy link
Contributor

shigeki commented Feb 9, 2015

Fixed in #762

@jbergstroem
Copy link
Member Author

Here's the result from the test after fixing path to openssl binary:

=== release test-tls-no-sslv3 ===                                              
Path: parallel/test-tls-no-sslv3
CONNECTED(00000003)
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : SSLv3
    Cipher    : 0000
    Session-ID: 
    Session-ID-ctx: 
    Master-Key: 
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time: 1423692122
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
---
assert.js:87
  throw new assert.AssertionError({
        ^
AssertionError: false == true
    at Server.<anonymous> (/home/jbergstroem/iojs/test/parallel/test-tls-no-sslv3.js:38:3)
    at Server.<anonymous> (/home/jbergstroem/iojs/test/common.js:268:15)
    at Server.g (events.js:240:16)
    at emitTwo (events.js:85:13)
    at Server.emit (events.js:153:7)
    at TLSSocket.<anonymous> (_tls_wrap.js:650:14)
    at emitOne (events.js:75:13)
    at TLSSocket.emit (events.js:150:7)
    at TLSSocket._tlsError (_tls_wrap.js:404:8)
    at TLSWrap.ssl.onerror (_tls_wrap.js:315:12)
140550306789008:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:s3_pkt.c:1456:SSL alert number 40
140550306789008:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:s3_pkt.c:644:
Command: out/Release/iojs /home/jbergstroem/iojs/test/parallel/test-tls-no-sslv3.js

@shigeki
Copy link
Contributor

shigeki commented Feb 12, 2015

@jbergstroem Thanks for your report. This error comes from the change of an error message in openssl-1.0.2 and it is to be fixed with shigeki@72031e6 after upgrading to openssl-1.0.2 . Please wait for a moment until I finish it.

@jbergstroem
Copy link
Member Author

@shigeki confirmed -- just tried with openssl 1.0.1l. I'm closing since we shouldn't assume 1.0.2 is working until that work is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tls Issues and PRs related to the tls subsystem.
Projects
None yet
Development

No branches or pull requests

3 participants