[infinispan-issues] [JBoss JIRA] (HRJS-29) Security related error messages vary between Node versions
Galder Zamarreño (JIRA)
issues at jboss.org
Fri Jan 6 07:04:00 EST 2017
[ https://issues.jboss.org/browse/HRJS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreño reassigned HRJS-29:
------------------------------------
Assignee: Galder Zamarreño
> Security related error messages vary between Node versions
> ----------------------------------------------------------
>
> Key: HRJS-29
> URL: https://issues.jboss.org/browse/HRJS-29
> Project: Infinispan Javascript client
> Issue Type: Bug
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 0.4.0
>
>
> Currently testsuite works fine with Node 0.10. When running for example with Node 4.x, you get errors like this:
> {code}
> 2) Infinispan TLS/SSL client can operate on data via crypto store trusted encrypted transport
> Message:
> Error: self signed certificate in certificate chain
> Stacktrace:
> Error: self signed certificate in certificate chain
> at Error (native)
> at TLSSocket.<anonymous> (_tls_wrap.js:1016:38)
> at emitNone (events.js:67:13)
> at TLSSocket.emit (events.js:166:7)
> at TLSSocket._finishInit (_tls_wrap.js:585:8)
> 3) Infinispan TLS/SSL client fails to operate if default server name (SNI) does not match default server realm
> Message:
> Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> Stacktrace:
> Error: Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> 4) Infinispan TLS/SSL client fails to operate if server name (SNI) and trusted certificate are incorrect
> Message:
> Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> Stacktrace:
> Error: Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> {code}
> So, the error message comparisons need to be adjusted to support other Node versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the infinispan-issues
mailing list