From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Justin Reeves <Justin.Reeves@cat.com>
Subject: Re: ECCN for Cygwin 1.7.34 - FREE
Date: Tue, 16 May 2023 11:47:49 -0600 [thread overview]
Message-ID: <53ab3beb-73a8-c43a-edf3-199aa40863f0@Shaw.ca> (raw)
In-Reply-To: <CA+kUOam08mkVVac6zfN8Jr_145=05fzqycJcJ4ovzbRYfy3hRA@mail.gmail.com>
On 2023-05-15 15:00, Adam Dinwoodie wrote:
> On Mon, 15 May 2023 at 21:46, Justin Reeves wrote:
>> I am a project manager at Caterpillar and I am working on compliance for programs/applications. I am looking to find the Electronic Classification Control Number (ECCN) for "Cygwin 1.7.34 - FREE". If someone could respond via email to confirm the ECCN, then I can document the response for this program and identify it properly in our various tools/databases. Please let me know if you need assistance. Thank you in advance for your help.
> Cygwin does not have an ECCN. There is more information on the website
> at https://cygwin.com/licensing.html
Justin,
Cygwin is a rolling release system which is designed to be updated regularly to
be compatible with any currently supported Windows (or Wine) releases.
Hundreds of serious security vulnerabilities have been fixed since 1.7.34:
194 update announcements since then have mentioned CVEs.
Cygwin has added supported for many Windows security features, deprecated and
dropped or upgraded vulnerable packages and features, and added a lot of other
newer standard security features since then; see:
https://cygwin.com/cygwin-ug-net/ov-new.html
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-05-16 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:45 Justin Reeves
2023-05-15 21:00 ` Adam Dinwoodie
2023-05-16 17:47 ` Brian Inglis [this message]
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=53ab3beb-73a8-c43a-edf3-199aa40863f0@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=Justin.Reeves@cat.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).