DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 544DnLhE016403
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 544DnLhE016403
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=dpTdt3gA
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 083343858C42
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1746366559;
	bh=KSpm5HyidzMoMAb4pVxTjv9LuHiR0L+J6tocIjIEewo=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=dpTdt3gAXXM3CP7u7+9L1kGqL/U57DbanG1XimXA2+JlD+t4/FyWt3sBFmiH8bYHD
	 IKKRC1ox0YtzoaaiibqH4lvWmcN6lpV9wdTaBK4v3A6Xg4Fh/ZyZC5j63Ghiiqmw8b
	 mPyb++lsnH3pJNcWUozLmBgWG5J7XEm1leSADDwI=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B1B6A3858D1E
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org B1B6A3858D1E
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1746366501; cv=none;
 b=s5t13sd0KobUKlqAZBCw6IFd39MRAlIMqebK4T9Op/oCqJXJ6+1F1tBTFp1rYO0trs/iBxh1CgD+hP7mteOGj4aknz2YbVTxLwKoToSRG+6bi7DIUM8RdMUfV769KET3VMI1TJnpjmqHwx/oSSiUJqeyG36eE69IIO8dVWa8u8w=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1746366501; c=relaxed/simple;
 bh=ZEsEjahlk0gduYvNiSSEQY4Ny7cKiNj0yOnJuyKEVkA=;
 h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature;
 b=R0rkMGGgfnAP9cSAqwDYPN0Gv716bgP5WoQUG7s39wPrONFZN4HgnBd3lpk2vEfX6pxhv10dhl53v5RVX8/xpAAMonSV0QxBdFeCnpp3tq2E7nJdkJkmhnn7rVw8yioqzwDPdsRSqwJaQk9kXun3C+NH9UO26GSQ00Ai0sjn8v8=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B1B6A3858D1E
Message-ID: <456b8493-8383-4d17-b4f4-f17cb99515b8@systematicsw.ab.ca>
Date: Sun, 4 May 2025 07:48:18 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Signing cygwin.com binaries with signtool by default ?
Content-Language: en-CA
To: cygwin AT cygwin DOT com
References: <5fd86c45-8236-43ce-b259-0e0145dda30f AT SystematicSW DOT ab DOT ca>
 <D943C328-6581-4334-B06F-860922EEF62B AT dgtlrift DOT com>
Organization: Systematic Software
In-Reply-To: <D943C328-6581-4334-B06F-860922EEF62B@dgtlrift.com>
X-Stat-Signature: y7nga3yg9jqc4rwrsz9mtdqqpuro4nn3
X-Rspamd-Server: rspamout06
X-Rspamd-Queue-Id: BF4FB6000F
X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361
X-Session-ID: U2FsdGVkX1/4EBoFt/y+7ClcrbBYxdaglF8o6/2SKTk=
X-HE-Tag: 1746366499-281189
X-HE-Meta: U2FsdGVkX19qcguSNYE+t/ztRToWw7w5NohNLRBKG/xYzmBfSo4gOJwS1JSc8Ara4MrRZBKVgIxdPG5KHm4BpM4zeLC7EPnHoWS1dvXat65mNyaOTeRrTbaC1YRsK9ANumbu+JQ3hBQBRVQOUJSasWKF5+HC51HTleK0MnKgwEPWGp3mcZkA6PI7m1tAJ7kRpETokKNkipUlSxRpZaPWMoXoTy80WstDnQneLY4pDpvQsBF3rv6GJhwDfDqGDqPTkn5MT1NxKstSNb4pae0tvljrh+RZPk+obthv4inbv7OUv943VnFB+YcUzwrdv0H9mc7ChmtHDWodHfHyOHZIFXKtk4OAj5Odrnjwv17CkQIGxRcPMX4w/HDu+XXufNzKiObRBABIjG644pJm7rM+4k0x0jlY8LtkRvfNuX4oMtMiFuLJj9NVd5dTDL1TPMfngzgEyiCk/llySXQMmBbVxwsuEEgu7wQ+
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
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: Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Brian Inglis <Brian DOT Inglis AT systematicsw DOT ab DOT ca>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 544DnLhE016403

Yes - Cygwin is licensed as GPL V3 or later
- and the DLL is LGPL V3 or later WITH Linking Exception;
see:
	https://cygwin.com/licensing.html

and the files CYGWIN_LICENSE, COPYING, COPYING.LIB, other instances of COPYING 
and LICENSE files in /usr/share/doc/**/ directories, especially cygwin and 
cygwin-doc, and copies in the headers of various source files.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


On 2025-05-04 04:37, James Hanley wrote:
> Break the license rules? How - is it GPLv3?
> -Jim
> 
>> On May 3, 2025, at 3:09 PM, Brian Inglis via Cygwin <cygwin AT cygwin DOT com> wrote:
>>
>> On 2025-05-03 12:21, Roland Mainz via Cygwin wrote:
>>> Is it somehow possible that the CI+Release binaries (*.exe, *.dll) can
>>> be signed with signtool
>>> (https://learn.microsoft.com/en-us/windows/win32/seccrypto/signtool)?
>>
>> No - would break the Cygwin licence terms unless MS releases source!
>>
>>> It seems that Microsoft Defender has become overly aggressive to some
>>> Cygwin binaries (mostly /usr/bin/hostname, /usr/bin/find, /usr/bin/tar
>>> etc.) in the last couple of weeks and just blocks them.
>>
>> Aha - more MS Embrace, Extend, Extinguish!
>>
>> Which Windows, Defender, and Cygwin releases did this start with?
>>
>> $ which -a find hostname tar | cyg-sanitize-output.sed
>> /usr/bin/find
>> /proc/cygdrive/c/WINDOWS/system32/find
>> /usr/bin/hostname
>> /proc/cygdrive/c/WINDOWS/system32/hostname
>> /usr/bin/tar
>> /proc/cygdrive/c/WINDOWS/system32/tar
>>
>> Perhaps Cygwin installer or cygcheck should start renaming MS Windows binaries whose names conflict with Cygwin utilities! ;^>
>>
>> What about other packages that install exes whose names conflict with MS Windows utilities - does MS block them also, or just Cygwin's, or also other open source; what about WSL installs?
>>
>> [I noticed today that MS supports using only its own proprietary FIDO passkey authenticator app - which nobody sensible would ever trust! I liked when we used to be able to delete MS crypto keys from the MS Windows keystore.]
>>
>>> Our IT supports that they can "whitelist" binaries based on their
>>> cryptographic signature... but neither the binaries from the CI nor
>>> the Release binaries have any signatures...
>>
>> Perhaps your paid IT support could just figure out how they could bypass Defender checking the Cygwin roots or /*bin/ dirs?
>>
>> I suspect many of us do that to reduce the overhead of the BLODA.
>>
>> Or perhaps your paid IT support could just figure out how they could provide their own Cygwin mirror with binaries signed with their own signatures and tools.
>>
>> Cygwin supports osslsigncode:
>>
>>     https://cygwin.com/packages/summary/osslsigncode-src.html
>>
>> OpenSSL-based Authenticode signing and timestamping tool
>>
>> Platform-independent tool for Authenticode signing of PE(EXE/SYS/DLL/etc), CAB and MSI files. It also supports timestamping (Authenticode and RFC3161).
>>
>> That would require our volunteers to find and spend more of their free time to integrate the tool into the package build processes, and it would not be available until the volunteers find more of their free time once the next release of each upstream package becomes available.

-- 
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