You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Charles Lamb (JIRA)" <ji...@apache.org> on 2014/05/29 02:42:04 UTC

[jira] [Updated] (HDFS-6392) Wire crypto streams for encrypted files in DFSClient

     [ https://issues.apache.org/jira/browse/HDFS-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Lamb updated HDFS-6392:
-------------------------------

    Attachment: HDFS-6392.1.patch

Taking [~andrew.wang]'s advice, I'm submitting this set of intermediate diffs for review. These wire the Crypto{Input/Output}Streams into the HDFS client; initialize the KeyProvider in the Namenode; carry the key/iv through the relevant client/namenode protocols; add a unit test for the streams.

Since this is only going on the branch, it shouldn't matter too much that all accesses to files are guaranteed to be encrypted or that the key/iv is hardwired everywhere.


>  Wire crypto streams for encrypted files in DFSClient
> -----------------------------------------------------
>
>                 Key: HDFS-6392
>                 URL: https://issues.apache.org/jira/browse/HDFS-6392
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode, security
>            Reporter: Alejandro Abdelnur
>            Assignee: Charles Lamb
>         Attachments: HDFS-6392.1.patch
>
>
> When the DFS client gets a key material and IV for a file being opened/created, it should wrap the stream with a crypto stream initialized with the key material and IV.



--
This message was sent by Atlassian JIRA
(v6.2#6252)