From: Philip Oakley <philipoakley@iee.email>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC] squelch log4j inquiries
Date: Fri, 24 Dec 2021 10:59:30 +0000 [thread overview]
Message-ID: <3c5ef210-8908-e96f-e201-a7d8e79985fb@iee.email> (raw)
In-Reply-To: <xmqqmtkq6frf.fsf@gitster.g>
On 23/12/2021 23:52, 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
Would it be worth adding a section to the SECURITY.md file that could
cover these 'non-issue' concerns. The README could point to the
non-issue section. Just a thought.
Philip
prev parent reply other threads:[~2021-12-24 10:59 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
2021-12-24 10:59 ` Philip Oakley [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=3c5ef210-8908-e96f-e201-a7d8e79985fb@iee.email \
--to=philipoakley@iee.email \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.