You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2019/09/29 22:30:00 UTC
[jira] [Assigned] (QPID-8354) [Broker-J][JMS AMQP 0-x] Backlist
TLSv1.1
[ https://issues.apache.org/jira/browse/QPID-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-8354:
--------------------------------
Assignee: Alex Rudyy
> [Broker-J][JMS AMQP 0-x] Backlist TLSv1.1
> -----------------------------------------
>
> Key: QPID-8354
> URL: https://issues.apache.org/jira/browse/QPID-8354
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J, JMS AMQP 0-x
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-client-0-x-6.4.0, qpid-java-broker-7.1.5, qpid-java-client-0-x-6.3.5
>
>
> The TLSv1.1 is allowed by default for establishing TLS connectivity in both Qpid Broker-J and legacy JMS client for AMQP 0-x. TLS 1.0 is already blacklisted in both products. We can consider restricting allowed TLS protocols to TLSv1.2 and TLSv1.3 by default. The TLSv1.2 can be used with JDK8-10 and TLSv1.3 can be used with JDK 11 and above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org