[ https://issues.apache.org/jira/browse/QPID-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940539#comment-16940539 ]
ASF subversion and git services commented on QPID-8353: ------------------------------------------------------- Commit d50617333ff52385e3316e11b135a57d1b0859b6 in qpid-jms-amqp-0-x's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=d506173 ] QPID-8353: [JMS AMQP 0-x] Add TLSv1.3 into preferences > [Broker-J][JMS AMQP 0-x] Add support for TLSv1.3 > ------------------------------------------------ > > Key: QPID-8353 > URL: https://issues.apache.org/jira/browse/QPID-8353 > Project: Qpid > Issue Type: Improvement > Components: Broker-J, JMS AMQP 0-x > Reporter: Alex Rudyy > Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.4 > > > As part of QPID-7056 the functionality for establishing TLS connectivity in > Qpid Broker-J and JMS client for AMQP 0-x have been changed to enforce > creation of SSLContext with a hard-coded sub-set of TLS protocols (TLSv1.2, > TLSv1.1, TLS, TLSv1). See {{SSLUtil#tryGetSSLContext()}}. As result, both > broker and client might not be able to establish TLSv1.3 connections when JDK > 11 or above is used unless TLSv1.2, TLSv1.1 are explicitly blacklisted. The > code needs to be improved to allow TLSv1.3. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org