[jira] [Commented] (ACCUMULO-958) Support pluggable encryption in walogs

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on ACCUMULO-958:
---------------------------------

Integrated in Accumulo-Trunk-Hadoop-2.0 #56 (See [https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/56/])
    ACCUMULO-958 marked incomplete WAL encrpytion feature as experimental so it will not show up in docs (Revision 1441504)

     Result = SUCCESS
kturner : 
Files : 
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/conf/DefaultConfiguration.java
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/conf/Property.java

                
> Support pluggable encryption in walogs
> --------------------------------------
>
>                 Key: ACCUMULO-958
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-958
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: logger
>            Reporter: John Vines
>            Assignee: Michael Allen
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-958-actual-changes.patch, accumulo-958.diff
>
>
> There are some cases where users want encryption at rest for the walogs. It should be fairly trivial to implement it in such a way to insert a CipherOutputStream into the data path (defaulting to using a NullCipher) and then making the Cipher pluggable to users can insert the appropriate mechanisms for their use case.
> This also means swapping in CipherInputStream and putting in a check to make sure the Cipher type's match at read and write time. Possibly a versioning mechanism so people can migrate Ciphers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira