You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2017/08/26 05:02:00 UTC
[jira] [Updated] (HDFS-12359) Re-encryption should operate with
minimum KMS ACL requirements.
[ https://issues.apache.org/jira/browse/HDFS-12359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HDFS-12359:
-----------------------------
Attachment: HDFS-12359.01.patch
Attach a patch for the fix:
- can (and should) simply drain the client cache without having to send a {{invalidateCache}} to the server. {{invalidateCache}} is the responsibility for key rolling.
- after cache is drained, generate a new edek, and use the version of that. This eliminates the need for {{getCurrentKey}}
> Re-encryption should operate with minimum KMS ACL requirements.
> ---------------------------------------------------------------
>
> Key: HDFS-12359
> URL: https://issues.apache.org/jira/browse/HDFS-12359
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: encryption
> Affects Versions: 3.0.0-beta1
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Attachments: HDFS-12359.01.patch
>
>
> This was caught from KMS acl testing.
> HDFS-10899 gets the current key versions from KMS directly, which requires {{READ}} acls.
> It also calls invalidateCache, which requires {{MANAGEMENT}} acls.
> We should fix re-encryption to not require additional ACLs than original encryption.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org