hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8275) Range check DelegationKey length
Date Tue, 01 May 2012 21:36:52 GMT

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

Hudson commented on HADOOP-8275:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #2169 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2169/])
    HADOOP-8275. Range check DelegationKey length. Contributed by Colin Patrick McCabe (Revision
1332839)

     Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332839
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/WritableUtils.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/DelegationKey.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestWritableUtils.java

                
> Range check DelegationKey length 
> ---------------------------------
>
>                 Key: HADOOP-8275
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8275
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HADOOP-8275.001.patch, HADOOP-8275.002.patch, HADOOP-8275.003.patch
>
>
> Harden serialization logic against malformed or malicious input.
> Add range checking to readVInt, to detect overflows, underflows, and larger-than-expected
values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message