You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "eric baldeschwieler (JIRA)" <ji...@apache.org> on 2012/07/11 05:19:36 UTC

[jira] [Commented] (MAPREDUCE-4417) add support for encrypted shuffle

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411198#comment-13411198 ] 

eric baldeschwieler commented on MAPREDUCE-4417:
------------------------------------------------

What is the driving use case?  

I'd suggest that anyone who wants the data encrypted on the wire, will want it encrypted at rest on both sides as well.  The data is as vulnerable there.  

I wonder if we can come up with an approach that just introduces new plugins and doesn't add any hadoop code?  The right thing is probably to use the compression codecs to encrypt on the way to disk.

thoughts?

                
> add support for encrypted shuffle
> ---------------------------------
>
>                 Key: MAPREDUCE-4417
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4417
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv2, security
>    Affects Versions: 2.0.0-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 2.0.1-alpha
>
>
> Currently Shuffle fetches go on the clear. While Kerberos provides comprehensive authentication for the cluster, it does not provide confidentiality. 
> When processing sensitive data confidentiality may be desired (at the expense of job performance and resources utilization for doing encryption).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira