Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 67971200D58 for ; Sun, 3 Dec 2017 00:21:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6611B160C19; Sat, 2 Dec 2017 23:21:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A947B160BFB for ; Sun, 3 Dec 2017 00:21:05 +0100 (CET) Received: (qmail 40582 invoked by uid 500); 2 Dec 2017 23:21:04 -0000 Mailing-List: contact dev-help@ranger.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ranger.apache.org Delivered-To: mailing list dev@ranger.apache.org Received: (qmail 40571 invoked by uid 99); 2 Dec 2017 23:21:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Dec 2017 23:21:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 10F271808A5 for ; Sat, 2 Dec 2017 23:21:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oQca5sf7MF6E for ; Sat, 2 Dec 2017 23:21:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 115915F47D for ; Sat, 2 Dec 2017 23:21:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 89113E015F for ; Sat, 2 Dec 2017 23:21:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B5BDA255BF for ; Sat, 2 Dec 2017 23:21:01 +0000 (UTC) Date: Sat, 2 Dec 2017 23:21:00 +0000 (UTC) From: "Abhay Kulkarni (JIRA)" To: dev@ranger.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (RANGER-1707) Traverse check in RangerHdfsAuthorizer works incorrectly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 02 Dec 2017 23:21:06 -0000 [ https://issues.apache.org/jira/browse/RANGER-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni reassigned RANGER-1707: -------------------------------------- Assignee: Abhay Kulkarni (was: Zsombor Gegesy) > Traverse check in RangerHdfsAuthorizer works incorrectly > -------------------------------------------------------- > > Key: RANGER-1707 > URL: https://issues.apache.org/jira/browse/RANGER-1707 > Project: Ranger > Issue Type: Bug > Components: plugins > Affects Versions: 1.0.0 > Reporter: Zsombor Gegesy > Assignee: Abhay Kulkarni > Labels: hdfs-2.8 > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1707-Fix-hdfs-traverse-check-which-problem-wa.patch, RANGER-1707-2.patch, RANGER-1707-3.patch > > > Traversal check in RangerHdfsAuthorizer works incorrectly, when it is asked for access to /a/b/c.txt, it only checks that if there are a policy which grants EXEC to /a/b, but if it there aren't any, then it doesn't check, if there is a policy which grants READ, WRITE or EXEC to /a/b/c.txt explicitly, which would mean, that the path is accessible to the user. > This hasn't noticed by the current unit tests, because HDFS before 2.8.0 doesn't called the traversal check before reading or writing a file, however it will cause problem with 2.8.0, where FSDirectory.resolvePath will perform a mandatory traversal check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)