From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/rsync: security bump to version 3.2.5
Date: Sat, 17 Sep 2022 17:27:29 +0200 [thread overview]
Message-ID: <87v8pm10ny.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220826214620.75193-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 26 Aug 2022 23:46:20 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Fix CVE-2022-29154: An issue was discovered in rsync before 3.2.5 that
> allows malicious remote servers to write arbitrary files inside the
> directories of connecting peers. The server chooses which
> files/directories are sent to the client. However, the rsync client
> performs insufficient validation of file names. A malicious rsync
> server (or Man-in-The-Middle attacker) can overwrite arbitrary files
> in the rsync client target directory and subdirectories (for example,
> overwrite the .ssh/authorized_keys file).
> - Drop patches (already in version)
> - Update hash of COPYING (make openssl license exception clearer by
> having it at the top and use modern links in COPYING:
> https://github.com/WayneD/rsync/commit/dde469513625c0e10216da9b6f6546aa844431f7)
> https://github.com/WayneD/rsync/blob/v3.2.5/NEWS.md
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-17 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 21:46 [Buildroot] [PATCH 1/1] package/rsync: security bump to version 3.2.5 Fabrice Fontaine
2022-08-27 7:53 ` Yann E. MORIN
2022-09-17 15:27 ` Peter Korsgaard [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=87v8pm10ny.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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.