public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: CYGWIN 2.8
Date: Mon, 14 May 2018 14:31:00 -0000	[thread overview]
Message-ID: <4c236fdb-c6c7-64a9-5a9b-4ee9d05b938b@gmail.com> (raw)
In-Reply-To: <18bf68cd-7681-2dcc-f360-252cbfeab7a7@t-online.de>

On 5/8/2018 3:28 PM, Hans-Bernhard Bröker wrote:
> Am 08.05.2018 um 13:22 schrieb David Spencer:
>> Morning,
>>
>> I am trying to get CYGWIN Version 2.8, this is the only version
>> approved for our system at present, 


So your company is stating it wants to use buggy and susceptible
applications.  I don't think so.  Go back to the IT security team and
state that 2.10 is the latest version of Cygwin and ask if it is okay.
If not then ask them to provide you with a suitable version.

>
> Providing that is, to a great extent, actually the job of whoever
> approves versions of Cygwin for you.
>

The company should provide a common mirror of approved applications.

> That's because the version number of cygwin itself barely begins to
> define an actual fixed configuration of the whole Cygwin environment
> you'll be installing: that's _one_ package whose version number has been
> nailed down, but _hundreds_ of others left totally floating.
> 

The version number of the Cygwin DLL doesn't provide the versions of all
of the components possible to use.  A company approving a specific
version of Cygwin DLL is clueless as to what Cygwin is.

> The only practical way of defining an installation of which it can even
> make sense to call it "approved" is to host a fixed mirror repository
> that's controlled by whoever does the approving, inside the organization
> that requires said approval.
> 

Exactly!

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-05-14 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 12:17 David Spencer
2018-05-08 13:04 ` Marco Atzeri
2018-05-14 17:05   ` Brian Inglis
2018-05-09  8:30 ` Hans-Bernhard Bröker
2018-05-14 14:31   ` cyg Simple [this message]
2018-05-14 19:30     ` Lee
2018-05-14 23:49       ` cyg Simple

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=4c236fdb-c6c7-64a9-5a9b-4ee9d05b938b@gmail.com \
    --to=cygsimple@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).