X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org ADD39385701E
Authentication-Results:	sourceware.org;
	dmarc=pass (p=none dis=none) header.from=yandex.ru
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=anrdaemon AT yandex DOT ru
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1605204300; bh=BuiPJRMbMpFocwLyfySuPdgd1RGZfqO0bCg5Kp0/qtI=;
	h=In-Reply-To:Subject:To:Reply-To:From:Message-ID:References:Date;
	b=MU1EYZtPbGeUn+kjUI9C7mfWMjJ80xVMvLjykIapBohchr/kgBiTqmW012NDSxaRn
	rj5IVRWaJ8O+TJaKlsZamU4cxu+vMvUEKk2S/Cx6g9C8UG2tYXOtbR8MoXWaQzDW7J
	X1Zeac5WiKhlXNjgXp5FXL2ctHP21nLZmo8zTcoE=
Authentication-Results:	mxback15o.mail.yandex.net;
	dkim=pass header.i=@yandex.ru
Date:	Thu, 12 Nov 2020 20:53:34 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
X-Mailer:	The Bat! (v6.8.8) Home
X-Priority:	3 (Normal)
Message-ID:	<1833090211.20201112205334@yandex.ru>
To:	Sudhanshu Bhutani <anshbhutani AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Regarding openssh 8.1p1-1 access
In-Reply-To:	<CAJh6wzsEYf4G75QeBf2J18zaw-W5d_8F2mNJaHgJjHr0Qc0Jgg@mail.gmail.com>
References:	<CAJh6wzvH76FHO5S4QEKFAU=75_UiTeCK8MaqRGM13GBf8NpH3Q AT mail DOT gmail DOT com>
	<a812c96a-5f24-cd91-9830-b2bd1427f62a AT SystematicSw DOT ab DOT ca>
	<CAJh6wzssyObRovM6LV6iz2GTHndbBxReKKqECU_XW5q8Ai87EA AT mail DOT gmail DOT com>
	<CAJh6wzsNQ2y_GYA_R87SWKLavB04P78X7pSgkNqVm_iCVLm41g AT mail DOT gmail DOT com>
	<319918437 DOT 20201111135657 AT yandex DOT ru>
	<CAJh6wzsEYf4G75QeBf2J18zaw-W5d_8F2mNJaHgJjHr0Qc0Jgg AT mail DOT gmail DOT com>
MIME-Version:	1.0
X-Spam-Status:	No, score=-1.8 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.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
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>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

Greetings, Sudhanshu Bhutani!

>> Greetings, Sudhanshu Bhutani!
>>
>> > On Tue, Nov 10, 2020 at 6:14 PM Sudhanshu Bhutani wrote:
>>
>> >> Thank you Brian and Mike. We will see if cygwin time machine owners can
>> >> help us.
>> >> http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html
>> >>
>> >> I will try contacting - doctor AT fruitbat DOT org - PETER CASTRO for any
>> help.
>> >>
>>
>> > One more approach - i was thinking was - can we package/include the
>> > complete cygwin already [which already has older openssh version in bin
>> > folder] installed folder to our tool exe without any modification?
>> > Does it involve any violations for Cygwin GPLv3? Do we need to include
>> > source code as well? Or can re-distributing an already created cygwin
>> > folder can be done with freedom without any issues?
>>
>> You can provide a private mirror of your own as suggested, which would be a
>> more future-proof way, but really you should investigate the cause of the
>> failing SSH behavior and fix THAT.
>> I suspect the fix would be way easier than setting up and maintaining a
>> whole
>> mirror.
>>
>>
> Thanks for your reply, we are going to retire our platform that uses ssh
> client of old times in next 4 months, which is not supporting updated
> ciphers/updated in openssh 8.2 versions. As cygwin is only supporting
> updated binaries from openssh and not listing older versions, hence the
> issue is appearing on the platform where old ssh client is deployed.
> Unfortunately, the platform lives with customer and we dont have any way to
> update obsolete platform. Hence, i was thinking for work around on this
> platform for next 4-6 months, to re-distribute already installed cygwin
> folder to customer from which our tool can use older ssh client.

I have an urge to call the b-word.

> Does it involve gplv3 violations or any legal challenge? Appreciate your
> response.

Newer OpenSSH do support old ciphers, but they needs to be explicitly enabled
in config.
See https://www.openssh.com/legacy.html


-- 
With best regards,
Andrey Repin
Thursday, November 12, 2020 20:09:31

Sorry for my terrible english...

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