hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10141) Create an API to separate encryption key storage from applications
Date Fri, 20 Dec 2013 00:29:08 GMT

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

Owen O'Malley updated HADOOP-10141:

       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

I just committed this. Thanks for the review, Jitendra.

> Create an API to separate encryption key storage from applications
> ------------------------------------------------------------------
>                 Key: HADOOP-10141
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10141
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 3.0.0
>         Attachments: h-10141.patch, hadoop-10141.patch, hadoop-10141.patch, hadoop-10141.patch
> As with the filesystem API, we need to provide a generic mechanism to support multiple
key storage mechanisms that are potentially from third parties. 
> An additional requirement for long term data lakes is to keep multiple versions of each
key so that keys can be rolled periodically without requiring the entire data set to be re-written.
Rolling keys provides containment in the event of keys being leaked.
> Toward that end, I propose an API that is configured using a list of URLs of KeyProviders.
The implementation will look for implementations using the ServiceLoader interface and thus
support third party libraries.
> Two providers will be included in this patch. One using the credentials cache in MapReduce
jobs and the other using Java KeyStores from either HDFS or local file system. 

This message was sent by Atlassian JIRA

View raw message