From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/tcpreplay: security bump to version 4.4.2
Date: Mon, 29 Aug 2022 09:01:20 +0200 [thread overview]
Message-ID: <20220829070120.GS37358@scaer> (raw)
In-Reply-To: <20220829061842.40771-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2022-08-29 08:18 +0200, Fabrice Fontaine spake thusly:
> Fix CVE-2022-25484, CVE-2022-27416, CVE-2022-27418, CVE-2022-27939,
> CVE-2022-27940, CVE-2022-27941, CVE-2022-27942, CVE-2022-28487,
> CVE-2022-37047, CVE-2022-37048, CVE-2022-37049
>
> https://github.com/appneta/tcpreplay/releases/tag/v4.4.2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/tcpreplay/tcpreplay.hash | 4 ++--
> package/tcpreplay/tcpreplay.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/tcpreplay/tcpreplay.hash b/package/tcpreplay/tcpreplay.hash
> index 32bfd219d4..97c2e7ee34 100644
> --- a/package/tcpreplay/tcpreplay.hash
> +++ b/package/tcpreplay/tcpreplay.hash
> @@ -1,5 +1,5 @@
> # Locally calculated after checking pgp signature
> -# https://github.com/appneta/tcpreplay/releases/download/v4.4.1/tcpreplay-4.4.1.tar.xz.asc
> +# https://github.com/appneta/tcpreplay/releases/download/v4.4.2/tcpreplay-4.4.2.tar.xz.asc
> # using key 84E4FA215C934A7D97DC76D5E9E2149793BDE17E
> -sha256 51f70ed14be5913f19c25cdfa530e98c14cedab1c76fbdd26eca7b61b57344f2 tcpreplay-4.4.1.tar.xz
> +sha256 91585c247b108ed3c10d3546d18f6a467d44229c9988c97736f953af69a6f438 tcpreplay-4.4.2.tar.xz
> sha256 07cf5e92d475287a7d1663b33097f40cae5adf03ed8920fcd4374e3dfb48c8ad docs/LICENSE
> diff --git a/package/tcpreplay/tcpreplay.mk b/package/tcpreplay/tcpreplay.mk
> index f228882ecc..65eb908932 100644
> --- a/package/tcpreplay/tcpreplay.mk
> +++ b/package/tcpreplay/tcpreplay.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -TCPREPLAY_VERSION = 4.4.1
> +TCPREPLAY_VERSION = 4.4.2
> TCPREPLAY_SITE = https://github.com/appneta/tcpreplay/releases/download/v$(TCPREPLAY_VERSION)
> TCPREPLAY_SOURCE = tcpreplay-$(TCPREPLAY_VERSION).tar.xz
> TCPREPLAY_LICENSE = GPL-3.0
> --
> 2.35.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-29 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 6:18 [Buildroot] [PATCH 1/1] package/tcpreplay: security bump to version 4.4.2 Fabrice Fontaine
2022-08-29 7:01 ` Yann E. MORIN [this message]
2022-09-17 20:23 ` 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=20220829070120.GS37358@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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