Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Titouan Christophe <titouanchristophe@gmail.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Daniel Price <daniel.price@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/redis: bump to v7.0.3
Date: Thu, 11 Aug 2022 21:00:11 +0200	[thread overview]
Message-ID: <5ea8dcb9-268e-c93c-d3dd-5a302c141b2d@gmail.com> (raw)
In-Reply-To: <871qtoqt9f.fsf@dell.be.48ers.dk>

Hello Peter and all,

I just sent the patch to the ML even before seeing your message below.

Could you also please backport it onto 2022.05.x ?

Best regards,

Titouan

On 10/08/22 12:37, Peter Korsgaard wrote:
>>>>>> "Titouan" == Titouan Christophe <titouanchristophe@gmail.com> writes:
>   > Signed-off-by: Titouan Christophe <titouanchristophe@gmail.com>
>
> Committed to 2022.05.x given the fixes, thanks.
>
> I see there is also a 7.0.4 release with security fixes, care to send a
> patch?
>
> ================================================================================
> Redis 7.0.4 Released Monday Jul 18 12:00:00 IST 2022
> ================================================================================
>
> Upgrade urgency: SECURITY, contains fixes to security issues.
>
> Security Fixes:
> * (CVE-2022-31144) A specially crafted XAUTOCLAIM command on a stream
>    key in a specific state may result with heap overflow, and potentially
>    remote code execution. The problem affects Redis versions 7.0.0 or
>    newer.
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-11 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 11:45 [Buildroot] [PATCH 1/1] package/redis: bump to v7.0.3 Titouan Christophe
2022-07-17 13:21 ` Yann E. MORIN
2022-08-10 10:37 ` Peter Korsgaard
2022-08-11 19:00   ` Titouan Christophe [this message]
2022-08-11 19:20     ` 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=5ea8dcb9-268e-c93c-d3dd-5a302c141b2d@gmail.com \
    --to=titouanchristophe@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox