[jira] [Issue Comment Deleted] (HADOOP-10153) Define Crypto policy interfaces and provide its default implementation.

["Owen O'Malley (JIRA)" <ji...@apache.org>]

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

Owen O'Malley updated HADOOP-10153:
-----------------------------------

    Comment: was deleted

(was: After looking at the javax.security.Cipher API more deeply, it does have both byte[] and ByteBuffer methods. 

Unfortunately the methods in Cipher are declared final and the actual implementation is done by a nested implementation class. It isn't clear what the performance penalty for using javax.security.Cipher with a openssl-based provider would be, but it doesn't look excessive.

My thoughts are that instead of reinventing the wheel, we should use the standard javax.security.Cipher API with a customer provider that is based on openssl.

Thoughts?)

> Define Crypto policy interfaces and provide its default implementation.
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-10153
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10153
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Yi Liu
>            Assignee: Yi Liu
>              Labels: rhino
>             Fix For: 3.0.0
>
>
> The JIRA defines crypto policy interface, developers/users can implement their own crypto policy to decide how files/directories are encrypted. This JIRA also includes a default implementation.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)