[
https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900521#comment-15900521
]
Abraham Fine commented on ZOOKEEPER-236:
----------------------------------------
[~hanm]-
bq. Separate configuration option provides better flexibility and is also
consistent with SASL / Kerberos configurations for client-server and
server-server.
That makes sense to me. I'll update the patch. I'm also taking suggestions for
what such an option should be named. :)
bq. unless it is trivial to implement and test rolling upgrade
It was pretty trivial to implement and I imagine testing should not be too
difficult either.
bq. Today we don't use Netty for server-server chat so it seems no immediate
needs to rely on Netty for this work.
This is how I feel as well. I'm sure we can pretty quickly come up with a list
of deficiencies in the current design but I don't think there is anything
severe enough at this moment to give us cause to rewrite right now.
> SSL Support for Atomic Broadcast protocol
> -----------------------------------------
>
> Key: ZOOKEEPER-236
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236
> Project: ZooKeeper
> Issue Type: New Feature
> Components: quorum, server
> Reporter: Benjamin Reed
> Assignee: Abraham Fine
> Priority: Minor
>
> We should have the ability to use SSL to authenticate and encrypt the traffic
> between ZooKeeper servers. For the most part this is a very easy change. We
> would probably only want to support this for TCP based leader elections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
