failed test: parallel/test-tls-0-dns-altname when using shared openssl

[jbergstroem]

Path: parallel/test-tls-0-dns-altname
assert.js:100
  throw new assert.AssertionError({
        ^
AssertionError: "DNS:google.com, DNS:just-another.com, IP Address:8.8.8.8, IP Address:8.8.4.4, DNS:last.com" == "DNS:google.com\u0000.evil.com, DNS:just-another.com, IP Address:8.8.8.8, IP Address:8.8.4.4, DNS:last.com"
    at TLSSocket.<anonymous> (test/parallel/test-tls-0-dns-altname.js:29:12)
    at TLSSocket.g (events.js:184:16)
    at TLSSocket.emit (events.js:95:17)
    at TLSSocket.<anonymous> (_tls_wrap.js:910:18)
    at TLSSocket.emit (events.js:95:17)
    at TLSSocket._finishInit (_tls_wrap.js:436:8)

The test checks for process.versions.openssl, which will always exist regardless of using a shared library or not. I'm not sure what we want to do here -- possibly just rewrite the check?

[shigeki]

@jbergstroem This error is confirmed in my Ubuntu 14.04 with OpenSSL 1.0.1f installed by apt-get. Is this the same environment as yours?

[jbergstroem]

@shigeki I have a newer openssl (OpenSSL 1.0.2 22 Jan 2015). Both this test and test-tls-no-sslv3 fails, but sslv3 at least fails because of the "right" reasons thanks to #762. I've also tested 1.0.1{j,k,l}.

[shigeki]

@jbergstroem Thanks. That means this error is independent of openssl version. I'll take a look at it.

[shigeki]

Fixed in #800 . Close this.
@jbergstroem Thanks for your reporting and I'd like you to confirm that it is really fixed.

[jbergstroem]

@shigeki confirmed fixed, thanks. test-tls-no-sslv3 still fails for me though -- I guess #618 ended up being used for fixing openssl-binary path. Do you want me to create a new issue?

[shigeki]

@jbergstroem I reopen #618 . Could you give me more information?

[jbergstroem]

@shigeki Sorry, snuck a link in above comment. I'll post it to the other issue.