From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/2] package/samba4: security bump to version 4.8.4
Date: Fri, 24 Aug 2018 23:07:59 +0200 [thread overview]
Message-ID: <20180824230759.097c0e18@windsurf> (raw)
In-Reply-To: <20180824162744.11726-1-bernd.kuhls@t-online.de>
Hello,
On Fri, 24 Aug 2018 18:27:43 +0200, Bernd Kuhls wrote:
> Release notes: https://www.samba.org/samba/history/samba-4.8.4.html
>
> Fixes
>
> o CVE-2018-1139 (Weak authentication protocol allowed.)
> o CVE-2018-1140 (Denial of Service Attack on DNS and LDAP server.)
> o CVE-2018-10858 (Insufficient input validation on client directory
> listing in libsmbclient.)
> o CVE-2018-10918 (Denial of Service Attack on AD DC DRSUAPI server.)
> o CVE-2018-10919 (Confidential attribute disclosure from the AD LDAP
> server.)
>
> Cherry-picked from master branch:
> https://git.buildroot.net/buildroot/commit/?id=3d7ce0124aa6ab116f430604db72c99bcd7a299a
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/samba4/samba4.hash | 4 ++--
> package/samba4/samba4.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
I've applied both to next (actually for the first patch, I did the
cherry-pick myself). However, I also cherry-picked
6d3723147659542ec1cba4139981d75413d89edc from master into next,
otherwise we would be having the same build failures on next that
6d3723147659542ec1cba4139981d75413d89edc was fixing.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-24 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 16:27 [Buildroot] [PATCH/next 1/2] package/samba4: security bump to version 4.8.4 Bernd Kuhls
2018-08-24 16:27 ` [Buildroot] [PATCH/next 2/2] package/samba4: bump version to 4.8.5 Bernd Kuhls
2018-08-24 21:07 ` Thomas Petazzoni [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=20180824230759.097c0e18@windsurf \
--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