Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1833525589.1213855425087.JavaMail.jira@brutus>
Date: Wed, 18 Jun 2008 23:03:45 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3578) mapred.system.dir should be
 accessible only to hadoop daemons
In-Reply-To: <1322367835.1213682984936.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hemanth Yamijala commented on HADOOP-3578:
------------------------------------------

bq. Only if their names are known. Since the directory cannot be listed except by owner, if random names are used, then others cannot remove them.

The names of the job directories start with job_. hadoop dfs -rmr job_* would remove them, right ? I tried it on my directories, and wild card removal of directories seems to be working. So, I am assuming it will work even for the mapred system directories children.

> mapred.system.dir should be accessible only to hadoop daemons 
> --------------------------------------------------------------
>
>                 Key: HADOOP-3578
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3578
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>
> Currently the jobclient accesses the {{mapred.system.dir}} to add job details. Hence the {{mapred.system.dir}} has the permissions of {{rwx-wx-wx}}. This could be a security loophole where the job files might get overwritten/tampered after the job submission. 

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