From: Andrey Repin <anrdaemon@yandex.ru>
To: Sudhanshu Bhutani <anshbhutani@gmail.com>, cygwin@cygwin.com
Subject: Re: Regarding openssh 8.1p1-1 access
Date: Wed, 11 Nov 2020 13:56:57 +0300 [thread overview]
Message-ID: <319918437.20201111135657@yandex.ru> (raw)
In-Reply-To: <CAJh6wzsNQ2y_GYA_R87SWKLavB04P78X7pSgkNqVm_iCVLm41g@mail.gmail.com>
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.
--
With best regards,
Andrey Repin
Wednesday, November 11, 2020 13:54:50
Sorry for my terrible english...
next prev parent reply other threads:[~2020-11-11 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 18:51 Sudhanshu Bhutani
2020-11-10 19:05 ` Marco Atzeri
2020-11-10 20:28 ` Sudhanshu Bhutani
2020-11-10 20:55 ` Mike O'Brien
2020-11-10 22:43 ` Brian Inglis
2020-11-10 23:14 ` Sudhanshu Bhutani
2020-11-11 0:16 ` Sudhanshu Bhutani
2020-11-11 4:26 ` Eliot Moss
2020-11-11 10:56 ` Andrey Repin [this message]
2020-11-11 13:59 ` Sudhanshu Bhutani
2020-11-12 17:53 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=319918437.20201111135657@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=anshbhutani@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).