From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rsync: security bump to version 3.1.3
Date: Sat, 10 Feb 2018 10:14:40 +0100 [thread overview]
Message-ID: <20180210101440.738778d6@windsurf.lan> (raw)
In-Reply-To: <958696d988eecdc48bea09ad76234933706a7e0a.1518153988.git.baruch@tkos.co.il>
Hello,
On Fri, 9 Feb 2018 07:26:28 +0200, Baruch Siach wrote:
> Fixes CVE-2018-5764: remote attackers can bypass an
> argument-sanitization protection mechanism
>
> Drop upstream patches.
>
> Add license file hash.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> .../0001-Check-fname-in-recv_files-sooner.patch | 45 ----------------------
> ...0002-Sanitize-xname-in-read_ndx_and_attrs.patch | 39 -------------------
> ...mon-filter-against-fnamecmp-in-recv_files.patch | 28 --------------
> ...ailing-0-when-receiving-xattr-name-values.patch | 33 ----------------
> package/rsync/rsync.hash | 5 ++-
> package/rsync/rsync.mk | 2 +-
> 6 files changed, 5 insertions(+), 147 deletions(-)
> delete mode 100644 package/rsync/0001-Check-fname-in-recv_files-sooner.patch
> delete mode 100644 package/rsync/0002-Sanitize-xname-in-read_ndx_and_attrs.patch
> delete mode 100644 package/rsync/0003-Check-daemon-filter-against-fnamecmp-in-recv_files.patch
> delete mode 100644 package/rsync/0004-Enforce-trailing-0-when-receiving-xattr-name-values.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-10 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 5:26 [Buildroot] [PATCH] rsync: security bump to version 3.1.3 Baruch Siach
2018-02-10 9:14 ` Thomas Petazzoni [this message]
2018-04-10 20:44 ` Peter Korsgaard
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=20180210101440.738778d6@windsurf.lan \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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