[
https://issues.apache.org/jira/browse/QPID-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7418:
-----------------------------
Fix Version/s: Future
> Delegate TLS peer hostname check back to platform (X509ExtendedTrustManager)
> ----------------------------------------------------------------------------
>
> Key: QPID-7418
> URL: https://issues.apache.org/jira/browse/QPID-7418
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Keith Wall
> Fix For: Future
>
>
> Currently the legacy Java client implements its own TLS peer hostname
> checking {{SSLUtil#verifyHostname(javax.net.ssl.SSLEngine,
> java.lang.String)}} . Since Java 1.7, the platform has the ability to
> perform the certificate hostname check itself, if enabled on the SSLEngine.
> This would simplify the client.
> See Qpid JMS Client
> {{org.apache.qpid.jms.transports.TransportSupport#createSslEngine(java.net.URI,
> javax.net.ssl.SSLContext,
> org.apache.qpid.jms.transports.TransportSslOptions)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
