[
https://issues.apache.org/jira/browse/ZOOKEEPER-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309658#comment-14309658
]
Hongchao Deng commented on ZOOKEEPER-2094:
------------------------------------------
I mean the null SSL context. I didn't have any opinion yet. So I am writing
documentation for possible behavior.
Here's what I thought:
1. Client
A null SSL context will cause a null pointer exception
2. Server
It will automatically fall back to non-SSL pipeline.
I am wondering if you have better idea to handle this such as stopping the
client/server from running.
> SSL feature on Netty
> --------------------
>
> Key: ZOOKEEPER-2094
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2094
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: server
> Affects Versions: 3.4.6, 3.5.0
> Reporter: Ian Dimayuga
> Assignee: Ian Dimayuga
> Fix For: 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2094.patch, ZOOKEEPER-2094.patch,
> ZOOKEEPER-2094.patch, ZOOKEEPER-2094.patch, ZOOKEEPER-2094.patch,
> ZOOKEEPER-2094.patch, ZOOKEEPER-2094.patch, test.cert, testKeyStore.jks,
> testTrustStore.jks, testUntrustedKeyStore.jks
>
>
> Add SSL handler to Netty pipeline, and a default X509AuthenticationProvider
> to perform authentication.
> Review board: https://reviews.apache.org/r/30576/diff/#
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
