From: Maxime Devos <maximedevos@telenet.be>
To: Zhu Zihao <all_but_last@163.com>, Greg Hogan <code@greghogan.com>
Cc: 55001@debbugs.gnu.org
Subject: [bug#55001] [PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765].
Date: Mon, 18 Apr 2022 20:03:16 +0200 [thread overview]
Message-ID: <e4945293a6cc01cddfeec4ddbbbcd8116954507b.camel@telenet.be> (raw)
In-Reply-To: <86mtgi8jjd.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Zhu Zihao schreef op di 19-04-2022 om 00:02 [+0800]:
>
> Hi.
>
> https://www.phoronix.com/scan.php?page=news_item&px=Git-CVE-2022-24765
>
> This article says "likely due to only affect Microsoft Windows". I
> haven't test this CVE on *nix systems.
>
> If it doesn't affect Guix systems, should I remove "[fixes
> CVE-2022-24765]" in the git commit message or leave it there?
According to <https://lwn.net/Articles/891112/#Comments> and its
comments, it affects ‘multi-user (*) Linux (**) systems’ as well, if
someone has their git repo inside /tmp. (Does anyone actually do
that?)
(*) I would think this includes otherwise single-user systems with a
compromised daemon as well?
(**) Presumably also GNU/Hurd and the BSDs.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-04-18 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 13:42 [bug#55001] [PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765] Zhu Zihao
[not found] ` <handler.55001.B.165028941728102.ack@debbugs.gnu.org>
2022-04-18 14:23 ` [bug#55001] Acknowledgement ([PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765].) Zhu Zihao
2022-04-18 17:33 ` Greg Hogan
2022-04-19 9:19 ` [bug#55001] gnu: git: Update to 2.36.0 [fixes CVE-2022-24765] Was: " Zhu Zihao
2022-04-19 14:08 ` Greg Hogan
2022-04-23 4:20 ` Zhu Zihao
2022-04-27 9:33 ` bug#55001: [PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765] Mathieu Othacehe
2022-04-18 15:53 ` [bug#55001] " Greg Hogan
2022-04-18 16:02 ` Zhu Zihao
2022-04-18 18:03 ` Maxime Devos [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4945293a6cc01cddfeec4ddbbbcd8116954507b.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55001@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=code@greghogan.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).