[
https://issues.apache.org/jira/browse/BOOKKEEPER-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707883#comment-15707883
]
Enrico Olivelli commented on BOOKKEEPER-588:
--------------------------------------------
Thank you [~kishorekasi]
I think we should use configuration entries instead of system property. There
is a switch (which defaults to false from 4.5.0) to pass all the system
properties to AbstractConfiguration, and so this will not be a problem for you.
We are not going to implement STARTTLS as in SMTP protocol. There will be no
negotiation by default. So I think we will not be vulnerable to that kind of
attacks.
On the client side we will add a configuration property "use TLS", with this
flag the client will consider OK only connections upgraded to TLS, and will
refuse to communicate on plain socket connections. The same can be implemented
on the Bookie side.
In order to make a rolling upgrade we can add some flag to relax this
constraint, but IMHO in a production full-TLS environment plain connections
will be dropped from both sides.
This weeks I have not much time to write down the code and submit a PR, my idea
is to merge the original patch and the Salesforce patch, and to introduce a TLS
Auth plugin. I will start as soon as I can
> SSL support
> -----------
>
> Key: BOOKKEEPER-588
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-588
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Ivan Kelly
> Assignee: Enrico Olivelli
> Fix For: 4.5.0
>
> Attachments: 0001-MutualTLS-for-Bookkeeper.patch,
> 0004-BOOKKEEPER-588-SSL-support-for-bookkeeper.patch
>
>
> SSL support using startTLS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
