DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 54DGYGcI1970506
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 54DGYGcI1970506
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=xrmvPm3j
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 170E33858CD1
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1747154055;
	bh=KIUHQYDlhztnYD+XwmwY6Dy72Z2r9naZcuUrMIBktBY=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=xrmvPm3jT75U4mGCpQNTx6P5iYIPdHiteRTgz//EUdArwNfdRNzCY8MvfM79f6AUw
	OZva2kMUiYTbraltdtyh7mShBb6HRb9yt4OK0RnUSjvqs7P4CEczbGTQ9qhvupBflW
	6H9OJgMlw2MKGmu2ZV2TVskWYQcUqxdrpb3UPDVI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 8A9FF3858D34
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 8A9FF3858D34
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1747153987; cv=none;
	b=kDoLrP/zH7Hmx6F9Ixe2ulRgrvEQKiSWEqrAO/2Yz+gqpUz+mOQyJR64Zqgm6FQ44r5cZViT49yUGAN2xWF9tzhVyTgD61DHEtpSlG+q+AEIyyO5c2d7MiIWu8462Sc/WdPwd0G7HGz9Ek9/P1an64mMIGJfqze9kiuJyxZSubs=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1747153987; c=relaxed/simple;
	bh=gDin05Kz16NCc3kPSF9lfvy5scMzj4c/5GrToofdETI=;
	h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
	b=BtPAj23rz1hcT46kH9pXcko5WSyrHC1DCSnpddakbGQ2QCYnchV8D6SVRj/Adw8ijA4zVn9BwdVwS0DWTmw/UmY1MEg84shQnQWFh3uHeuTLcZ5pm0qzU8EF2CfPDE/NRzsFKPjjEjLA7mY597BFJw/WHWn5QVo96pgfxbKZG6g=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 8A9FF3858D34
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20230601; t=1747153987; x=1747758787;
	h=content-transfer-encoding:to:subject:message-id:date:from
	:in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
	:subject:date:message-id:reply-to;
	bh=pI894XAT64fB3JuC7Mv7/04F5JfMvH8kQ8EZe+UWJTs=;
	b=KrHF4WUA4XsTMvVbzGRa86wGHkei3NKM3N05axNzVjoARmApUsbvfXipfA5z/0K6f4
	L8fNEvCBSk6wLm5lpFOcaU40HWXXfljtMceg5EgQJYsxtGUjoOSfcAmZB0/wcTeD9qFR
	WBkP4X2tmvRGzlC3Y0gMowmQ5pU1RwCtUWa1yjRBfdbFlyNt7m6gPxUnR3G/FBV2CbYc
	xa/r4h8Xbx34Fttr+b6kEvdM8fiTQhlybIfslOo0w9bbAbo5Tq/lPCpM0ihVqk2QhNcN
	t6uNt4i41Fz7+ZfKp/mcw+CCOzj4Ix0oJJaxcBVAJep//cV/uCFz+j5SPAFIL3Etc80X
	+HHg==
X-Gm-Message-State:	AOJu0Yy3oGF02bFwRz5uG6HICXu8fWVhCFACB+MrvPkl6+KgNu5FtCGC
	MnxSqEviax3HG3rLvfXB1guerF3x4tBim+QJUfeNcZHLax3efr+bU81yp0tnnPX0+CWvBcpscG3
	6a6H18zDgwgb3x1K60ebovcstE5t5c1AU
X-Gm-Gg:	ASbGncvxlSLEVFpAlW9ntpOxRbTOts9Ii+0wCMMVcq3fgjWyw4vv7py7p0dseaZImjD
	xOn0bAaJBAxih063d6FYkwP7dScrU7DDFnRLz+nAg+Cct/V2dK0cYDytZ+AcQDihmLsg2jM/NQt
	cXJ7P0GToIyt2p5blg8DCmvtWCdmMB9aOH
X-Google-Smtp-Source:	AGHT+IEgp+cuk/T5p5wL3/araEnN7EpNsXg4u8GZkAKdgM1A3oHY4kbTp7faDS43a8wTGFy9aeDaMjp5KDAKMMkyDpU=
X-Received:	by 2002:a05:6870:596:b0:2d5:4f4:e24d with SMTP id
	586e51a60fabf-2dba41f21b1mr10862530fac.6.1747153986439; Tue, 13 May 2025
	09:33:06 -0700 (PDT)
MIME-Version:	1.0
References:	<CA+1jF5oPR8s20fEpadcdpE8TA+H_0P-inL8sSax7zz3QAcxLWg AT mail DOT gmail DOT com>
	<6ec5c987-b2ff-421d-b8f4-8b1ee7dca29c AT SystematicSW DOT ab DOT ca>
	<CA+1jF5orHBdQ3fQOY7FVGYwQYpVWS=TFnXbtcwxHh512fr4hQw AT mail DOT gmail DOT com>
	<8c0312e1-a37d-433a-bea2-6eec96eda5af AT SystematicSW DOT ab DOT ca>
In-Reply-To:	<8c0312e1-a37d-433a-bea2-6eec96eda5af@SystematicSW.ab.ca>
Date:	Tue, 13 May 2025 18:32:29 +0200
X-Gm-Features:	AX0GCFt8IKjBFdeB2VAf58BfhakOjhzN6UBru4QXERdYkiqjx-Cgc9fvH4G3LFs
Message-ID:	<CA+1jF5pfP1543kQz4X=2xVHuoH-Yfh1n1ntXkabSc++B_DU_Uw@mail.gmail.com>
Subject:	Re: Using Cygwin installation on network share in CI fails
To:	cygwin AT cygwin DOT com
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	=?utf-8?q?Aur=C3=A9lien_Couderc_via_Cygwin?= <cygwin AT cygwin DOT com>
Reply-To:	=?UTF-8?Q?Aur=C3=A9lien_Couderc?= <aurelien DOT couderc2002 AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 54DGYGcI1970506

On Tue, May 13, 2025 at 5:41 PM Brian Inglis via Cygwin
<cygwin AT cygwin DOT com> wrote:
>
> On 2025-05-13 02:33, Aurélien Couderc via Cygwin wrote:
> > On Mon, May 12, 2025 at 7:43 PM Brian Inglis via Cygwin wrote:
> >> On 2025-05-12 10:34, Aurélien Couderc via Cygwin wrote:
> >>> Using Cygwin install on network share in CI fails.
> >>> This seems to be a recent regression, as this was working a year before.
>
> If you have not run it in a year, it is possibly many things have changed in
> your environment.

The CI runs for *every* commit, with hundreds of commits a day.

My... crime... was to update Cygwin to Cygwin 3.6.1. After that,
Cygwin no longer works on WIndows network shares.

> >>> Now on Windows 10 with Cygwin 3.6.1 it fails with error 127.
> >> That can mean a missing DLL function entry.
>
> > No, I do not think so, as Cygwin works fine if I install it on NTFS.
>
> So you are not installing it on NTFS?
> What kind of share are you installing it on?

Windows 10 Enterprise (NT-10.0-19045), we use net use N: ... to mount
the standard Windows network share. AFAIK this is Server Message Block
3.1.

>
> Are you installing it using the *latest* download of Cygwin Setup from
>
>         https://cygwin/com/setup_x86_64.exe

Yes, indeed, we did.

>
> Do the installed files have all their read and exec bits set - this was an issue
> with a recent older release of Cygwin Setup where some files did not.

Yes, all DLL files have, per icacls, at least RX (read, execute) set.

> > WIndows DLLS should be fine, and the system is up to date with patches
> > and has a support contract.
>
> Should be is not definite!
> Patches have been known to cause issues!
> Does the support contract cover supporting the execution of Cygwin and utilities?

I can ask Microsoft support, but seriously for Microsoft "Cygwin" is a
3rd-party product.

>
> > But Cygwin fails if I install it on a Windows network share. Same
> > installation procedure (.\setup-x86_64.exe -q --no-write-registry
> > --no-admin --root %cd%
> > --no-desktop --site "https://mirrors.kernel.org/sourceware/cygwin"),
> > just different drive (N: instead of C:)
>
> A verbal description of a common failure is inadequate.
> We are not mind readers and have no idea how your CI environment is set up.
> Everything works fine in our CI environment, so your environment is defective,
> and we have no information allowing us to do more than speculate and suggest
> what may be an issue.
>
> It appears possible it is an issue with how the share you are using as a network
> drive is now set up.
> It may have been changed recently due to some process or policy change by your
> IT department.
> Please ask them what they have done recently that might affect the share you
> have been using successfully since 2016.
>
> Also please note that recent Windows changes have started blocking Cygwin
> programs with the same names as programs provided by MS (as outdated and
> insecure versions) like bash, curl, ssh*, tar, etc. possibly under the Windows
> security heading of Tamper Protection?

I turned off WIndows Defender, for testing purposes, and the result is the same.

> You have failed to respond to requests for actual information about or from the
> failing environment.
> We need to see actual output from commands of the file system properties and
> directory contents and permissions.

There *IS* no output. Everything which depends on cygwin1.dll just
fails without output.

> Maybe follow the problem reporting guidelines to run cygcheck -hrsv in the CI
> and include the output as a plain text attachment to your post.

I need to anonymise that, or IT will want my reprimation.

But the steps I posted fail on ANY Windows 10 and Windows 11 machine I
have tested so far, Windows Home, Enterprise and Pro.
All you need are the steps I posted, the KEY being doing an
installation on Windows Server Message Block filesystem. That is all.

Aurélien

P.S: I hereby propose a cygcheck -A (anonymise) option, which should
replace hostname, IP addresses and other sensitive data with one way
hashes like MD4 or MD5
-- 
Aurélien Couderc <aurelien DOT couderc2002 AT gmail DOT com>
Big Data/Data mining expert, chess enthusiast

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -