[jira] [Commented] (HDFS-6134) Transparent data at rest encryption

[Yi Liu (JIRA)]

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

Yi Liu commented on HDFS-6134:
------------------------------

[~yoderme], isn’t the same as I state?
Also the result
{code}
C1 xor C2 = P1 xor P2
{code}
isn’t {code} P2 = C2 xor (C1 xor P1){code} ?
My point is to guess P2, we should know P1.  (Absolutely we know C1, C2)
CTR attack is not by finding existing two cipher-text using same encryption key 
and same IV, it’s by ability of constructing file and make it encrypted by same 
Data key and IV.  If we can construct P1, then we know it. 


> Transparent data at rest encryption
> -----------------------------------
>
>                 Key: HDFS-6134
>                 URL: https://issues.apache.org/jira/browse/HDFS-6134
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: security
>    Affects Versions: 2.3.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: HDFSDataatRestEncryptionProposal_obsolete.pdf, 
> HDFSEncryptionConceptualDesignProposal-2014-06-20.pdf
>
>
> Because of privacy and security regulations, for many industries, sensitive 
> data at rest must be in encrypted form. For example: the health­care industry 
> (HIPAA regulations), the card payment industry (PCI DSS regulations) or the 
> US government (FISMA regulations).
> This JIRA aims to provide a mechanism to encrypt HDFS data at rest that can 
> be used transparently by any application accessing HDFS via Hadoop Filesystem 
> Java API, Hadoop libhdfs C library, or WebHDFS REST API.
> The resulting implementation should be able to be used in compliance with 
> different regulation requirements.



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