From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] memcached: bump to version 1.5.6
Date: Sun, 08 Apr 2018 21:40:03 +0200 [thread overview]
Message-ID: <87a7udbi7g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180402114204.3bbac3b4@windsurf> (Thomas Petazzoni's message of "Mon, 2 Apr 2018 11:42:04 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
> 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(-)
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-04-08 19:40 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 ` [Buildroot] [PATCH 1/2] memcached: bump to version 1.5.6 Thomas Petazzoni
2018-04-08 19:40 ` Peter Korsgaard [this message]
-- 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=87a7udbi7g.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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