Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 26 Jan 2013 00:51:12 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12627215.1357924648559.194093.1359161472460@arcas>
In-Reply-To: <JIRA.12627215.1357924648559@arcas>
References: <JIRA.12627215.1357924648559@arcas>
Subject: [jira] [Commented] (ACCUMULO-958) Support pluggable encryption in
 walogs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser commented on ACCUMULO-958:
-------------------------------------

I don't think there's a single answer to that, but it depends on the complexity of the feature. I'm being snarky because after the feature freeze was extended a week, we finally see the patch. Your point about it being in X time earlier is what I'm trying to point out.

We still have the ability to review this even after the feature freeze happens, it's just frustrating from my point of view in generating the best 1.5.0 candidate possible (we tend to go through x.y.0 releases pretty darn quick).
                
> 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