From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Iyana Garry <igarry@nardelloandco.com>
Subject: Re: Inquiry on Apache Log4j's Effect on Cygwin Software
Date: Thu, 23 Dec 2021 09:15:57 -0700 [thread overview]
Message-ID: <ce027305-0c14-f920-3f15-3250a1edf345@SystematicSw.ab.ca> (raw)
In-Reply-To: <MW5PR16MB4715B5B954FCFE75D451F6E7D77E9@MW5PR16MB4715.namprd16.prod.outlook.com>
On 2021-12-23 08:19, Iyana Garry wrote:
> Is there any confirmation that Cygwin software is not impacted by
> the Apache Log4J vulnerabilities (CVE-2021-44228, CVE-2021-45046 and
> CVE-2021-45105)?
Cygwin neither supports nor packages Java or log4j (Log for Java).
--
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.]
prev parent reply other threads:[~2021-12-23 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 15:19 Iyana Garry
2021-12-23 15:43 ` Bill Stewart
2021-12-23 15:47 ` Eliot Moss
2021-12-23 16:15 ` 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=ce027305-0c14-f920-3f15-3250a1edf345@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=igarry@nardelloandco.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).