From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-043.btinternet.com (mailomta26-re.btinternet.com [213.120.69.119]) by sourceware.org (Postfix) with ESMTPS id 40B2A3858D38 for ; Sat, 1 Oct 2022 15:37:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 40B2A3858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-001.btmx-prd.synchronoss.net ([10.2.54.4]) by re-prd-fep-043.btinternet.com with ESMTP id <20221001153716.TXIH3055.re-prd-fep-043.btinternet.com@re-prd-rgout-001.btmx-prd.synchronoss.net>; Sat, 1 Oct 2022 16:37:16 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A8CC33C322D5E X-Originating-IP: [81.153.98.187] X-OWM-Source-IP: 81.153.98.187 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvfedrfeehhedgudduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepffekiefgudejheetudeigfejledtleegleetkeduteeftdfffefhueefgfeutedtnecukfhppeekuddrudehfedrleekrddukeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdeingdpihhnvghtpeekuddrudehfedrleekrddukeejpdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdpnhgspghrtghpthhtohepvddprhgtphhtthhopefuthhrohhmvghkohesnhgvgihgohdruggvpdhrtghpthhtoheptgihghifihhnqdgrphhpshestgihghifihhnrdgtohhm X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.106] (81.153.98.187) by re-prd-rgout-001.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A8CC33C322D5E; Sat, 1 Oct 2022 16:37:16 +0100 Message-ID: <0c8c757c-4f6b-3b49-5404-99353de48b1b@dronecode.org.uk> Date: Sat, 1 Oct 2022 16:37:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Subject: Re: [Bug] setup regression #2 Content-Language: en-GB To: Achim Gratz , "cygwin-apps@cygwin.com" References: <87pmfn5o2j.fsf@Rainer.invalid> From: Jon Turney In-Reply-To: <87pmfn5o2j.fsf@Rainer.invalid> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3569.9 required=5.0 tests=BAYES_00,FORGED_SPF_HELO,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,NICE_REPLY_A,RCVD_IN_BARRACUDACENTRAL,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 22/09/2022 18:14, Achim Gratz wrote: > > The release_2.91 comes with another regression that still puzzles me. > In a nutshell, the three commits that deal with setting up the groups > during / after installation > > 2022-08-27 Jon Turney Drop setting root_scope as a side-effect of read_mounts() > 2022-08-16 Jon Turney Defer setting group until after All Users/Just For... > 2022-08-16 Jon Turney Drop group change while running postinstall scripts > > break existing installs in certain circumstances that are not yet > completely clear. The server installation @work (which uses exactly the > same scripting around the installation that I use for my build system > @home) changed from using the "Domain Users" group to "Administrators". > Additionally the previous access for "Everyone" has been removed and > instead SYSTEM is now part of the (Windows) ACL. In effect certain > files have become inaccessible to the normal users (unless they are aso > Administrators), in particular (this is the part that I still don't > understand) newly created symlinks can't be read by a normal user even > when the target is fully accessible. Even doing an ls on such a symlink > gets a "permission denied". This problem is with files created by setup, or by post-install scripts? (I'm not sure how these commits could have caused the former, if the latter then reverting 45d8e84e "Drop group change while running postinstall scripts" would be the thing to try...)