[
https://issues.apache.org/jira/browse/ACCUMULO-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951070#comment-13951070
]
John Vines commented on ACCUMULO-2587:
--------------------------------------
That makes sense, but should not always be the case. If the data is already
encrypted, we should give the users the ability to not pay an unnecessary
second encryption penalty
> Provide authentication criteria between a master and slave
> ----------------------------------------------------------
>
> Key: ACCUMULO-2587
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2587
> Project: Accumulo
> Issue Type: Sub-task
> Reporter: Josh Elser
> Fix For: 1.7.0
>
>
> Not necessarily needed for a first implementation, but, in the end, we should
> have some sort of authentication mechanism to prevent unwanted 3rd parties
> from interacting with a slave, injecting "fake replication" data.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
