From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-announce@cygwin.com
Subject: Security update: Git v2.35.3-1
Date: Thu, 14 Apr 2022 14:01:21 +0100 [thread overview]
Message-ID: <20220414130121.czttrtehqw2ylwy6@lucy.dinwoodie.org> (raw)
Version 2.35.3-1 of Git has been uploaded and should be coming soon to a
mirror near you.
This is an update to the latest upstream release; it contains two fixes,
one improving the security of yesterday's security fix for
CVE-2022-24765, and one improving the usability of that fix:
> * The code that was meant to parse the new `safe.directory`
> configuration variable was not checking what configuration
> variable was being fed to it, which has been corrected.
>
> * '*' can be used as the value for the `safe.directory` variable to
> signal that the user considers that any directory is safe.
This update includes the following patches:
- git
- git-cvs
- git-debuginfo
- git-email
- git-gui
- gitk
- git-p4
- git-svn
As ever, the full upstream changelogs are available with the source package, or
at:
https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes
https://github.com/git/git/tree/master/Documentation/RelNotes
Enjoy!
reply other threads:[~2022-04-14 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220414130121.czttrtehqw2ylwy6@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.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).