public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: CYGWIN 2.8
Date: Mon, 14 May 2018 19:30:00 -0000	[thread overview]
Message-ID: <CAD8GWsvDRXLgdZHie9pxweiB-RPfx=vX-E+6Nh_GsdUhtMNskw@mail.gmail.com> (raw)
In-Reply-To: <4c236fdb-c6c7-64a9-5a9b-4ee9d05b938b@gmail.com>

On 5/14/18, cyg Simple   wrote:
> 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.

And I don't think you've ever experienced the joys of being a USG contractor :)

Go back to the original post & look at their email address.  I'm
betting they're a contractor.

>  Go back to the IT security team and
> state that 2.10 is the latest version of Cygwin and ask if it is okay.

Which is assuming that whatever person on the IT security team you ask
has the authority to override policy.  Staff _follows_ policy, they
don't make it.

> If not then ask them to provide you with a suitable version.

You seem to be under the impression that contractors are allowed to
make waves and stay employed there.

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

I'd say it's the job of whoever came up with the policy of having an
'approved software' list in the first place to also come up with a
policy of keeping the list current but whatever..


It'd be nice to think the situation has changed in the years since I
was in the same position but apparently not.  What worked for me was
opening a support ticket with the group that keeps the approved
software list and asking what it takes to get the current version of
cygwin approved.

There's forms to be filled out, procedures to be followed, and in a
few weeks the current version of cygwin is on the approved list.

Regards,
Lee

--
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 19:29 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
2018-05-14 19:30     ` Lee [this message]
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='CAD8GWsvDRXLgdZHie9pxweiB-RPfx=vX-E+6Nh_GsdUhtMNskw@mail.gmail.com' \
    --to=ler762@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).