Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-8349

reinstate use of SSLSocket for cluster communication

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      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.

       

       

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            bschuchardt Bruce J Schuchardt
            bschuchardt Bruce J Schuchardt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment