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

Alex Rudyy edited comment on QPID-8153 at 4/4/18 12:27 PM:
-----------------------------------------------------------

Robbie,

JMS AMQP 0-x client does not set hostname/port on creation of SSLEngine as per 
[org.apache.qpid.transport.network.security.SecurityLayerFactory|https://github.com/apache/qpid-jms-amqp-0-x/blob/master/client/src/main/java/org/apache/qpid/transport/network/security/SecurityLayerFactory.java].
 It creates SSLEngine with {{SSLContext#createSSLEngine()}}.


was (Author: alex.rufous):
Robbie,

JMS AMQP 1-0 client does not set hostname/port on creation of SSLEngine as per 
[org.apache.qpid.transport.network.security.SecurityLayerFactory|https://github.com/apache/qpid-jms-amqp-0-x/blob/master/client/src/main/java/org/apache/qpid/transport/network/security/SecurityLayerFactory.java].
It creates SSLEngine with {{SSLContext#createSSLEngine()}}.

> [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 extension.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to