[
https://issues.apache.org/jira/browse/ACCUMULO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739146#comment-13739146
]
Michael Berman commented on ACCUMULO-1009:
------------------------------------------
Another outstanding issue is that the mechanism by which mapreduce jobs are
distributed to tasktrackers is a man-in-the-middle-able vector. I'm not sure
how to address that besides making the location the client looks for
truststores completely unconfigurable from the job config. At the moment, you
can't inject novel trust along the wire, but if you have write access anywhere
on the tasktracker node, you could point the tasks to a local truststore of
your choosing. What do people think? Would keeping the trusted roots on HDFS
be any better? Should you be able to configure where truststores are allowed
to be loaded from? (although not through job config, of course) Better ideas?
> Support encryption over the wire
> --------------------------------
>
> Key: ACCUMULO-1009
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1009
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Keith Turner
> Assignee: Michael Berman
> Fix For: 1.6.0
>
> Attachments: ACCUMULO-1009_thriftSsl.patch
>
>
> Need to support encryption between ACCUMULO clients and servers. Also need
> to encrypt communications between server and servers.
> Basically need to make it possible for users to enable SSL+thrift.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
