[
https://issues.apache.org/jira/browse/MAPREDUCE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758610#action_12758610
]
Owen O'Malley commented on MAPREDUCE-1026:
------------------------------------------
1. Of course
2. I'm pretty agnostic what the authentication mechanism is, other than I don't
want an extra round trip. I don't see any way of doing a hash without an extra
round trip on the connection open. On the other hand, doing a password doesn't
reveal anything that isn't already known. If the attacker can sniff the
network, they already know the secret.
3. If there is a better key length, we can use it. 66^10 is big enough to be
safe.
4. Of course
5. The key is per a job of course, but there is no advantage to having the
JobTracker pick it. Either way it will be framework code that picks it. Putting
it in the job conf is easy, and secure (once MAPREDUCE-181 goes in). Given that
the key will be at the JobTracker and all of the TaskTracker's, I don't see the
submitting node as a problem.
> Shuffle should be secure
> ------------------------
>
> Key: MAPREDUCE-1026
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1026
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: security
> Reporter: Owen O'Malley
> Assignee: Devaraj Das
>
> Since the user's data is available via http from the TaskTrackers, we should
> require a job-specific secret to access it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
