[
https://issues.apache.org/jira/browse/MAPREDUCE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999994#comment-12999994
]
Hadoop QA commented on MAPREDUCE-2103:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12459276/mapreduce-2103.txt
against trunk revision 1074251.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/64//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/64//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/64//console
This message is automatically generated.
> task-controller shouldn't require o-r permissions
> -------------------------------------------------
>
> Key: MAPREDUCE-2103
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2103
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task-controller
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Attachments: mapreduce-2103.txt, mapreduce-2103.txt
>
>
> The task-controller currently checks that "other" users don't have read
> permissions. This is unnecessary - we just need to make it's not executable.
> The debian policy manual explains it well:
> {quote}
> Setuid and setgid executables should be mode 4755 or 2755 respectively, and
> owned by the appropriate user or group. They should not be made unreadable
> (modes like 4711 or 2711 or even 4111); doing so achieves no extra security,
> because anyone can find the binary in the freely available Debian package; it
> is merely inconvenient. For the same reason you should not restrict read or
> execute permissions on non-set-id executables.
> Some setuid programs need to be restricted to particular sets of users, using
> file permissions. In this case they should be owned by the uid to which they
> are set-id, and by the group which should be allowed to execute them. They
> should have mode 4754; again there is no point in making them unreadable to
> those users who must not be allowed to execute them.
> {quote}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
