From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) by sourceware.org (Postfix) with ESMTPS id 5CFB8393BC29 for ; Thu, 8 Apr 2021 05:48:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5CFB8393BC29 Received: by mail-ej1-x631.google.com with SMTP id mh7so899363ejb.12 for ; Wed, 07 Apr 2021 22:48:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9ZgJ0+Bioqfq9wZA+7Hwwta9lS0u6ufmMyPTDtvf5YI=; b=DuH1WaWe6cRW//xgO9Kcr2dT74kVTjTw0noytazXTJh9u2kUZZn6pspql6kFDQ24Tj K60dbWK524VugEAIuAmBEH4L5QfBof0BG/m3Vz8q0x35Lcb1BYklZKJInKGnpiNad4Bc i+MAa8QVoTU98YR3wFpQGpI01o6Dl0Azqrn/2d5vcCq5Zjem/0KesC/paEJnUvYK9diX Mre+QBIJ37pm90HmnCEayWHvLgdlow1zfhnqkHkZKOuB03auSDqR/RD39fp//O+8gIl4 QIKmagD3LlyoOxLQClWqek6ZoIHNbHJ08zPg9HsBirjmFBU6R1xfe6uH+/seNf2G7czl XUig== X-Gm-Message-State: AOAM531vZBSJEvbENK9t58Y3f73usgKiRPfWJtzjxb/mqJQs/+ylsMZB Sr3sL/8A1RnqJkUip9l0D75Jj65LcXsw7g== X-Google-Smtp-Source: ABdhPJyl7WswEvvPqfA1loFety9kKKGaJreZUeeZ8c/oWjIKt7oBuMP0yNmpfZQh45+gqtdoyiVX0Q== X-Received: by 2002:a17:907:367:: with SMTP id rs7mr8222804ejb.192.1617860925460; Wed, 07 Apr 2021 22:48:45 -0700 (PDT) Received: from ?IPv6:2003:cc:9f36:b8fd:34dd:60a3:cc78:2d36? (p200300cc9f36b8fd34dd60a3cc782d36.dip0.t-ipconnect.de. [2003:cc:9f36:b8fd:34dd:60a3:cc78:2d36]) by smtp.gmail.com with ESMTPSA id b13sm2843507edw.45.2021.04.07.22.48.45 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Apr 2021 22:48:45 -0700 (PDT) Subject: Re: A problem with noacl+umask+chmod result To: cygwin@cygwin.com References: From: Marco Atzeri Message-ID: <7538d457-4b3e-1e01-d578-7415af235e34@gmail.com> Date: Thu, 8 Apr 2021 07:48:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2021 05:48:48 -0000 On 07.04.2021 22:47, Orgad Shaneh via Cygwin wrote: > Hi, > > If a filesystem is mounted with noacl, calling chmod to add write > permissions after umasking this permission doesn't work. Demonstrated > with command-line and C++. > > Did I miss something or is this a real bug? According to umask man, it > should only affect newly created files and directories, but I didn't > find anything that relates to chmod. > without ACL you can not expect the POSIX scheme to properly work. see https://cygwin.com/cygwin-ug-net/ntsec.html to understand how Cygwin uses ACL to mimic POSIX premissions