From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [RFC] squelch log4j inquiries
Date: Thu, 23 Dec 2021 19:14:57 -0500 [thread overview]
Message-ID: <01d201d7f85b$4bffb2c0$e3ff1840$@nexbridge.com> (raw)
In-Reply-To: <xmqqmtkq6frf.fsf@gitster.g>
On December 23, 2021 6:52 PM, Junio C Hamano wrote:
> I wonder if we should do something like this, for limited time like a few
> months or so, so that we have something prominently shown at places like
> https://github.com/git/git/
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> README.md | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git c/README.md w/README.md
> index f6f43e78de..76e99fe5bb 100644
> --- c/README.md
> +++ w/README.md
> @@ -7,6 +7,9 @@ Git is a fast, scalable, distributed revision control
system
> with an unusually rich command set that provides both high-level
operations
> and full access to internals.
>
> +No part of Git is written in Java, hence it is not susceptible to the
> +log4j vulnerability that has been causing sensation recently.
> +
> Git is an Open Source project covered by the GNU General Public License
> version 2 (some parts of it are under different licenses, compatible with
the
> GPLv2). It was originally written by Linus
This is a good idea. I have had to reassure a whole bunch of people in my
community about this, not really because of git itself but because of the
Maven build associated with EGit/JGit that may (do) have this issue if the
wrong version of log4j is available. I would rather not discuss the
particulars of the attack vector in this mailing list.
--Randall
next prev parent reply other threads:[~2021-12-24 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 23:52 [RFC] squelch log4j inquiries Junio C Hamano
2021-12-24 0:14 ` rsbecker [this message]
2021-12-25 0:38 ` Junio C Hamano
2021-12-24 10:59 ` Philip Oakley
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='01d201d7f85b$4bffb2c0$e3ff1840$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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