hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber
Date Fri, 30 May 2014 21:28:01 GMT

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

Alejandro Abdelnur commented on HADOOP-10611:
---------------------------------------------

[~andrew.wang], how about tackling that in a diff JIRA?

> KMS, keyVersion name should not be assumed to be keyName@versionNumber
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-10611
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10611
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: HADOOP-10611.patch
>
>
> Some KMS classes are assuming the keyVersion is keyName@versionNumber. 
> The keyVersion should be handled as an opaque value.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message