qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPIDJMS-391) Add support for the use of native OpenSSL based providers
Date Thu, 02 Aug 2018 20:31:00 GMT

     [ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish updated QPIDJMS-391:
---------------------------------
    Summary: Add support for the use of native OpenSSL based providers  (was: Add support
for SSL provider netty-tcnative-boringssl-static)

> Add support for the use of native OpenSSL based providers
> ---------------------------------------------------------
>
>                 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
>             Fix For: 0.36.0
>
>
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message