qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake
Date Wed, 04 Apr 2018 08:41:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425193#comment-16425193

Robbie Gemmell commented on QPID-8153:

I haven't tried this but the JIRA surprised me as last I saw the code it seemed like it should
work. SNI is done implicitly by the JVM if a hostname is passed to the SSLEngine when created.
Note that it only works for FQDN's, so using "localhost" wont but "localhost.localdomain"
will, in keeping with the SNI RFC. You can also explicitly set the SNI value used via configuration
objects on Java 8+ though.

> [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake
> -------------------------------------------------------------------------------
>                 Key: QPID-8153
>                 URL: https://issues.apache.org/jira/browse/QPID-8153
>             Project: Qpid
>          Issue Type: Improvement
>          Components: JMS AMQP 0-x
>    Affects Versions: qpid-java-client-0-x-6.3.0
>            Reporter: Alex Rudyy
>            Priority: Trivial
>             Fix For: qpid-java-client-0-x-6.3.1
> Qpid JMS AMQP 0-x client does not provide SNI as part of TLS handshake. The a client
should be able to indicate which hostname it is attempting to connect to by using SNI TLS

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message