From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward500o.mail.yandex.net (forward500o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::610]) by sourceware.org (Postfix) with ESMTPS id 2AA603858C2C for ; Wed, 26 Jan 2022 17:35:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2AA603858C2C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yandex.ru Received: from iva5-f582c699c75d.qloud-c.yandex.net (iva5-f582c699c75d.qloud-c.yandex.net [IPv6:2a02:6b8:c0c:5a18:0:640:f582:c699]) by forward500o.mail.yandex.net (Yandex) with ESMTP id A3A4394275B; Wed, 26 Jan 2022 20:35:01 +0300 (MSK) Received: from iva5-057a0d1fbbd8.qloud-c.yandex.net (iva5-057a0d1fbbd8.qloud-c.yandex.net [2a02:6b8:c0c:7f1c:0:640:57a:d1f]) by iva5-f582c699c75d.qloud-c.yandex.net (mxback/Yandex) with ESMTP id hmJvywYxL8-Z1cmiOIx; Wed, 26 Jan 2022 20:35:01 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1643218501; bh=4dzthm5jCoPMU6vnE1TGiA+KNdgz2OOFiVOgjV2uzYI=; h=In-Reply-To:Subject:From:Message-ID:References:Date:Reply-To:To; b=v/yOkVuODhNZd+AMrQQETVwKDNljKGA0jZtaLz0tu2bvXNTCXLk/YFMujmDFrWgeB +pjLcu6pjgsNF/UnkoILkehyRUOVeanQpOcWteeFRWDuEKRkabY6H01oinRfUDbOGK 6mZgozamsKsVe5HzLs3NzNC78a5P9lZbathUOBIE= Authentication-Results: iva5-f582c699c75d.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by iva5-057a0d1fbbd8.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id JwQIAKBca1-Z1JuMDcV; Wed, 26 Jan 2022 20:35:01 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) X-Yandex-Fwd: 2 Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Wed, 26 Jan 2022 17:34:02 -0000 Date: Wed, 26 Jan 2022 20:34:02 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home Reply-To: cygwin@cygwin.com X-Priority: 3 (Normal) Message-ID: <786598409.20220126203402@yandex.ru> To: mail2spam@gmx.net, cygwin@cygwin.com Subject: Re: Is Cygwin in any way affected by "Log4j" / "Log4Shell"...??? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Wed, 26 Jan 2022 17:35:04 -0000 Greetings, mail2spam@gmx.net! Since Cygwin(as a library/wrapper layer) is not packaging or in any other way providing Java code, no. As a software distribution platform, there are 33 packages that contain .jar files: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=%5C.jar%24&arch=x86_64 What they are doing and if they are susceptible to the exploit - a question to the relevant package author(s). -- With best regards, Andrey Repin Wednesday, January 26, 2022 20:20:45 Sorry for my terrible english...