You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce J Schuchardt (Jira)" <ji...@apache.org> on 2020/09/01 14:44:00 UTC
[jira] [Closed] (GEODE-8349) reinstate use of SSLSocket for cluster
communication
[ https://issues.apache.org/jira/browse/GEODE-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce J Schuchardt closed GEODE-8349.
-------------------------------------
> reinstate use of SSLSocket for cluster communication
> ----------------------------------------------------
>
> Key: GEODE-8349
> URL: https://issues.apache.org/jira/browse/GEODE-8349
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
> Labels: no-release-note, pull-request-available
>
> We've found problems with "new IO"'s SSLEngine with respect to support for TLSV1. We've also seen anomalous performance using that secure communications mechanism. The introduction of the use of the "new IO" SSLEngine was originally to 1) reduce code complexity in the org.apache.geode.internal.tcp package and 2) to set the stage for its use in client/server communications so that selectors could be used in c/s communications.
> This ticket aims to reintroduce the use of SSLSocket in cluster communications without restoring the old, poorly tested SSL code paths. The new implementation should have as good or better performance than the previous"old IO" implementation and the more recent "new IO" SSLEngine implementation as well. This should be apparent in the CI benchmark jobs.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)