Return-Path: 
 <user-return-10581-apmail-hadoop-hdfs-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4B42810D9B
	for <apmail-hadoop-hdfs-user-archive@minotaur.apache.org>;
 Wed,  4 Sep 2013 03:32:01 +0000 (UTC)
Received: (qmail 82945 invoked by uid 500); 4 Sep 2013 03:31:55 -0000
Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org
Received: (qmail 82647 invoked by uid 500); 4 Sep 2013 03:31:45 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Delivered-To: moderator for user@hadoop.apache.org
Received: (qmail 911 invoked by uid 99); 3 Sep 2013 20:09:53 -0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of meltrash@gmail.com designates
 209.85.215.67 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=gQwNl4gjePwcfJMkVZAOcRAgW8w5h9uLv6KX5r6UcoU=;
        b=ftB0PCkIZhoIY/pVFBW1A++zF2y4Gc9MO4WZ08YN6/5uQ/QgNu9OHZD/TDj94oufb7
         V3V/CPJwFnmB8ukcjFRGVIW9YKrPqffRaPDnHackKz1yrrtMmmt4LWXMfiOQ0+apUbpe
         nPwzsoL/AwrMT0mlQIsqGSr8EXSg8PXLzugs/7qAPdYbzUqgU9LAXjPLAkTTLQVrahV0
         EqCVyP1v3aPLb6AnjsX5Kc7Hmhwlc4bB1tAtd2YOwYbYutSuiPdi5x5v3gsM17SK/apP
         LunHxaulrXwrK52BXIsNa72PW9z302T5x6h+EWToqQlxCx3FRFYCya7NP8015vQ8HjX7
         tKpw==
MIME-Version: 1.0
X-Received: by 10.152.21.165 with SMTP id w5mr3280168lae.33.1378238967143;
 Tue, 03 Sep 2013 13:09:27 -0700 (PDT)
Date: Tue, 3 Sep 2013 22:09:27 +0200
Message-ID: 
 <CACj5vuDqHROCGzSRs39ddJY2sofrw-uzkUcgjxUC76t0NYkf4g@mail.gmail.com>
Subject: forbid use of hadoop.job.ugi to impersonate user without Kerberos
From: fred th <meltrash@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=089e0158b6dc0d624804e5804423
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0158b6dc0d624804e5804423
Content-Type: text/plain; charset=ISO-8859-1

Hello,
I'm considering using hadoop for a share cluster. As start to setup quickly
the system I'm was planning to differ Kerberos use.
Is there other way than using Kerberos to forbid a user to use
hadoop.job.ugi parameter to impersonate another user?

thanks
Mt

--089e0158b6dc0d624804e5804423
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div>I&#39;m considering using hadoop for a share cl=
uster. As start to setup quickly the system I&#39;m was planning to differ =
Kerberos use.=A0</div><div>Is there other way than using Kerberos to forbid=
 a user to use hadoop.job.ugi parameter to impersonate another user?</div>
<div><br></div><div>thanks</div><div>Mt</div></div>

--089e0158b6dc0d624804e5804423--