hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8658) Add support for configuring the encryption algorithm used for Hadoop RPC
Date Wed, 08 Aug 2012 13:42:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431110#comment-13431110

Aaron T. Myers commented on HADOOP-8658:

Hi Amol, if you haven't already, you should read through the dialogue on HDFS-3637.

What I mean by "on the wire" is as opposed to "at rest," i.e. the data is encrypted while
it is being transmitted over the network between clients and DNs, but not encrypted when the
data is stored on disk.

By "block data," I mean as opposed to the RPC data. When security is enabled, encrypting the
RPC traffic between clients and the NN, or DNs to the NN can already be encrypted. But, until
HDFS-3637 was implemented, there was no support for encrypting the actual file data being
read or written by clients and DNs.

The purpose of this JIRA is to add support for configuring the encryption algorithm used for
encrypting RPC traffic.
> Add support for configuring the encryption algorithm used for Hadoop RPC
> ------------------------------------------------------------------------
>                 Key: HADOOP-8658
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8658
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc, security
>    Affects Versions: 2.0.0-alpha
>            Reporter: Aaron T. Myers
>            Assignee: Joey Echeverria
> HDFS-3637 recently introduced the ability to encrypt actual HDFS block data on the wire,
including the ability to choose which encryption algorithm is used. It would be great if Hadoop
RPC similarly had support for choosing the encryption algorithm.

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


View raw message