hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6058) The TaskTracker's shell environment should not be passed to the children.
Date Wed, 17 Jun 2009 05:20:07 GMT

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

Devaraj Das commented on HADOOP-6058:
-------------------------------------

So this feature (or bug) to do with the whole of TaskTracker's env being passed to the child
has always been there. The fix to this issue (after an offline discussion with Owen) is:
1) Determine what env vars can be whitelisted
2) Disable variable substitution for the non-whitelisted ones and only do a pass-through (if
the user passes them via -Dmapred.child.env)

> The TaskTracker's shell environment should not be passed to the children.
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-6058
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6058
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
>            Priority: Critical
>             Fix For: 0.21.0
>
>
> HADOOP-2838 and HADOOP-5981 added support to make the TaskTracker's shell environment
available to the tasks. This has two problems:
>   1. It makes the task tracker's environment part of the interface to the task, which
is fairly brittle.
>   2. Security code typically only passes along whitelisted environment variables instead
of everything to prevent accidental leakage from the administrator's account.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message