From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] memcached: bump to version 1.5.6
Date: Mon, 2 Apr 2018 11:42:04 +0200 [thread overview]
Message-ID: <20180402114204.3bbac3b4@windsurf> (raw)
In-Reply-To: <20180302180756.14315-1-chrismcc@gmail.com>
Hello,
On Fri, 2 Mar 2018 10:07:55 -0800, Christopher McCrory wrote:
> From ReleaseNotes156
>
> This is a bugfix release, but it primarily disables the UDP protocol by
> default.
>
> In the last few days reports of UDP amplification attacks utilizing
> inesure memcached instances have surfaced. Attackers are able to set
> large values into memcached, then send requests via spoofed UDP packets.
> Memcached will then send a very large number of very large UDP packets
> back in response.
>
> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
> ---
> package/memcached/memcached.hash | 7 +++----
> package/memcached/memcached.mk | 2 +-
> 2 files changed, 4 insertions(+), 5 deletions(-)
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-04-02 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 18:07 [Buildroot] [PATCH 1/2] memcached: bump to version 1.5.6 Christopher McCrory
2018-03-02 18:07 ` [Buildroot] [PATCH 2/2] apache: pass explicit sbindir Christopher McCrory
2018-03-02 18:11 ` Christopher McCrory
2018-10-20 22:26 ` Arnout Vandecappelle
2018-04-02 9:42 ` Thomas Petazzoni [this message]
2018-04-08 19:40 ` [Buildroot] [PATCH 1/2] memcached: bump to version 1.5.6 Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 18:18 Christopher McCrory
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=20180402114204.3bbac3b4@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 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.