All of lore.kernel.org
 help / color / mirror / Atom feed
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/sngrep: security bump to version 1.7.0
Date: Fri, 15 Sep 2023 23:24:05 +0200	[thread overview]
Message-ID: <20230915212405.GF2571@scaer> (raw)
In-Reply-To: <20230915171631.896844-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2023-09-15 19:16 +0200, Fabrice Fontaine spake thusly:
> Fix CVE-2023-31981 and CVE-2023-31982
> 
> https://github.com/irontec/sngrep/blob/v1.7.0/ChangeLog
> https://github.com/irontec/sngrep/compare/v1.6.0...v1.7.0
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/sngrep/sngrep.hash | 6 +++---
>  package/sngrep/sngrep.mk   | 2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/package/sngrep/sngrep.hash b/package/sngrep/sngrep.hash
> index 60a32022e6..c9b9c8be8d 100644
> --- a/package/sngrep/sngrep.hash
> +++ b/package/sngrep/sngrep.hash
> @@ -1,6 +1,6 @@
> -# From https://github.com/irontec/sngrep/releases/download/v1.6.0/sngrep-1.6.0.tar.gz.md5sum
> -md5  1519ca6cd1167c0722debfb96e2ac173  sngrep-1.6.0.tar.gz
> +# From https://github.com/irontec/sngrep/releases/download/v1.7.0/sngrep-1.7.0.tar.gz.md5sum
> +md5  ee3cc7bd75adeb713411aa678e45ae4c  sngrep-1.7.0.tar.gz
>  
>  # Locally computed
> -sha256  fd80964d6560f2ff57b4f5bef2353d1a6f7c48d2f1a5f0a167c854bd2e801999  sngrep-1.6.0.tar.gz
> +sha256  2e5ba3a4d6486ea00bd73d2cceff383ba162dcd6d0170ae74cfa3b1c206e2cb1  sngrep-1.7.0.tar.gz
>  sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  LICENSE
> diff --git a/package/sngrep/sngrep.mk b/package/sngrep/sngrep.mk
> index 0e344550d3..b86d7e83f0 100644
> --- a/package/sngrep/sngrep.mk
> +++ b/package/sngrep/sngrep.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -SNGREP_VERSION = 1.6.0
> +SNGREP_VERSION = 1.7.0
>  SNGREP_SITE = \
>  	https://github.com/irontec/sngrep/releases/download/v$(SNGREP_VERSION)
>  SNGREP_LICENSE = GPL-3.0+
> -- 
> 2.40.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

  reply	other threads:[~2023-09-15 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 17:16 [Buildroot] [PATCH 1/1] package/sngrep: security bump to version 1.7.0 Fabrice Fontaine
2023-09-15 21:24 ` Yann E. MORIN [this message]
2023-09-24 18:42 ` 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=20230915212405.GF2571@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 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.