[
https://issues.apache.org/jira/browse/HDFS-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979486#comment-16979486
]
Steve Loughran commented on HDFS-13617:
---------------------------------------
Just catching up on this while looking at changelogs and noticing about what
happened to Token
Can I ask that when HDFS- work goes near stuff in hadoop-common -and anything
which goes into the security modules qualifies- that this is not done in an
HDFS JIRA, but in a HADOOP- one? Because that way it is invisible to more than
just the HDFS team, and we get to provide our input, including concerns about
whether this was going to be compatible with every other use of Token.
I am glad that the followup patch moved the changes out, so I don't have to
worry about it. But please, can we have a bit more cross-project visibility to
fundamental changes to some of Hadoop's primary data structures for which
over-the-wire compatibility is critical.
Thanks.
> Allow wrapping NN QOP into token in encrypted message
> -----------------------------------------------------
>
> Key: HDFS-13617
> URL: https://issues.apache.org/jira/browse/HDFS-13617
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-13617.001.patch, HDFS-13617.002.patch,
> HDFS-13617.003.patch, HDFS-13617.004.patch, HDFS-13617.005.patch,
> HDFS-13617.006.patch, HDFS-13617.007.patch, HDFS-13617.008.patch,
> HDFS-13617.009.patch
>
>
> This Jira allows NN to configurably wrap the QOP it has established with the
> client into the token message sent back to the client. The QOP is sent back
> in encrypted message, using BlockAccessToken encryption key as the key.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
