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 07A9F200D11 for ; Mon, 2 Oct 2017 15:27:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 060351609DE; Mon, 2 Oct 2017 13:27:12 +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 4B49F1609EF for ; Mon, 2 Oct 2017 15:27:11 +0200 (CEST) Received: (qmail 34725 invoked by uid 500); 2 Oct 2017 13:27:10 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 34713 invoked by uid 99); 2 Oct 2017 13:27:10 -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; Mon, 02 Oct 2017 13:27:10 +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 954A11953F4 for ; Mon, 2 Oct 2017 13:27:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id reFwk5D1eOkf for ; Mon, 2 Oct 2017 13:27:08 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 31BC05FE02 for ; Mon, 2 Oct 2017 13:27:08 +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 938D7E0EB9 for ; Mon, 2 Oct 2017 13:27:06 +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 E3254242C4 for ; Mon, 2 Oct 2017 13:27:00 +0000 (UTC) Date: Mon, 2 Oct 2017 13:27:00 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-14768) Honoring sticky bit during Deletion when authorization is enabled in WASB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 02 Oct 2017 13:27:12 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-14768: ------------------------------------ Status: Open (was: Patch Available) > Honoring sticky bit during Deletion when authorization is enabled in WASB > ------------------------------------------------------------------------- > > Key: HADOOP-14768 > URL: https://issues.apache.org/jira/browse/HADOOP-14768 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure > Affects Versions: 2.8.1 > Reporter: Varada Hemeswari > Assignee: Varada Hemeswari > Labels: fs, secure, wasb > Attachments: HADOOP-14768.001.patch, HADOOP-14768.002.patch, HADOOP-14768.003.patch, HADOOP-14768.003.patch, HADOOP-14768.004.patch, HADOOP-14768.004.patch, HADOOP-14768.005.patch, HADOOP-14768.006.patch, HADOOP-14768.007.patch, HADOOP-14768-branch-2-008.patch, HADOOP-14768-branch-2-009.patch > > > When authorization is enabled in WASB filesystem, there is a need for stickybit in cases where multiple users can create files under a shared directory. This additional check for sticky bit is reqired since any user can delete another user's file because the parent has WRITE permission for all users. > The purpose of this jira is to implement sticky bit equivalent for 'delete' call when authorization is enabled. > Note : Sticky bit implementation for 'Rename' operation is not done as part of this JIRA -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org