From: Sudhanshu Bhutani <anshbhutani@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Regarding openssh 8.1p1-1 access
Date: Tue, 10 Nov 2020 19:16:27 -0500 [thread overview]
Message-ID: <CAJh6wzsNQ2y_GYA_R87SWKLavB04P78X7pSgkNqVm_iCVLm41g@mail.gmail.com> (raw)
In-Reply-To: <CAJh6wzssyObRovM6LV6iz2GTHndbBxReKKqECU_XW5q8Ai87EA@mail.gmail.com>
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?
On Tue, Nov 10, 2020 at 6:14 PM Sudhanshu Bhutani <anshbhutani@gmail.com>
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.
>
>
> On Tue, Nov 10, 2020 at 5:44 PM Brian Inglis <
> Brian.Inglis@systematicsw.ab.ca> wrote:
>
>> On 2020-11-10 11:51, Sudhanshu Bhutani via Cygwin wrote:
>> > My name is Sudhanshu Bhutani and we are working for one of leading
>> network
>> > service providers for our internal telecom tool. For the last few days,
>> our
>> > customers are reporting problems with our internal tool which uses
>> cygwin
>> > ssh and posix components.
>> >
>> > We have a problem reported in the cygwin installation procedure, where
>> > openssh 8.1p1-1 is not getting downloaded and cygwin mirrors are not
>> > listing this 8.1p1-1 version and instead latest versions are listed.
>> >
>> > How can we download 8.1p1-1 in cygwin?
>>
>> Security software like openssh should always be kept up to date to fix
>> issues
>> and plug vulnerabilities which could allow yourself and your clients'
>> systems to
>> be compromised. Cygwin typically only provides and allows the current and
>> two
>> previous versions to be installed, in this case 8.4, 8.3, 8.2. Version
>> 8.1 is
>> over a year old and should no longer be used; see:
>>
>> https://www.openssh.com/releasenotes.html
>>
>> If you are concerned about how this is managed by Cygwin, you should
>> provide
>> your own Cygwin package repository mirror, where you can control which
>> packages
>> and versions are provided and made available.
>>
>> --
>> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>>
>> This email may be disturbing to some readers as it contains
>> too much technical detail. Reader discretion is advised.
>> [Data in binary units and prefixes, physical quantities in SI.]
>> --
>> 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
>>
>
>
> --
> Regards
> Sudhanshu Bhutani
>
--
Regards
Sudhanshu Bhutani
next prev parent reply other threads:[~2020-11-11 0:16 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 [this message]
2020-11-11 4:26 ` Eliot Moss
2020-11-11 10:56 ` Andrey Repin
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=CAJh6wzsNQ2y_GYA_R87SWKLavB04P78X7pSgkNqVm_iCVLm41g@mail.gmail.com \
--to=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).