[
https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Stenberg updated QPIDJMS-391:
---
Labels: performance (was: )
Description:
It would be great to have an option to use netty-tcnative-boringssl-static
instead of the java based SSL provider. In the ActiveMQ Artemis this was
implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649
In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration was
introduced. https://github.com/netty/netty/pull/8084
was:It would be great to have an option to use
netty-tcnative-boringssl-static instead of the java based SSL provider. In the
ActiveMQ Artemis this was implemented as part of
https://issues.apache.org/jira/browse/ARTEMIS-1649
> Add support for SSL provider netty-tcnative-boringssl-static
>
>
> Key: QPIDJMS-391
> URL: https://issues.apache.org/jira/browse/QPIDJMS-391
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
>Reporter: Johan Stenberg
>Priority: Minor
> Labels: performance
>
> It would be great to have an option to use netty-tcnative-boringssl-static
> instead of the java based SSL provider. In the ActiveMQ Artemis this was
> implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649
> In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration
> was introduced. https://github.com/netty/netty/pull/8084
--
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
