Re: Regarding openssh 8.1p1-1 access

[Andrey Repin <anrdaemon@yandex.ru>]

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@fruitbat.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...