Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: [RFC] squelch log4j inquiries
Date: Fri, 24 Dec 2021 16:38:52 -0800	[thread overview]
Message-ID: <xmqqo8551psz.fsf@gitster.g> (raw)
In-Reply-To: <01d201d7f85b$4bffb2c0$e3ff1840$@nexbridge.com> (rsbecker@nexbridge.com's message of "Thu, 23 Dec 2021 19:14:57 -0500")

<rsbecker@nexbridge.com> writes:

>> +No part of Git is written in Java, hence it is not susceptible to the
>> +log4j vulnerability that has been causing sensation recently.
>> +
> ...
> 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.

As you can point those people at the message that started this
thread at the lore archive, I actually think that I already have
done enough to achieve our goal ;-)




  reply	other threads:[~2021-12-25  0:38 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
2021-12-25  0:38   ` Junio C Hamano [this message]
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=xmqqo8551psz.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.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