From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, Marek Belisko <marek.belisko@open-nandra.com>
Subject: Re: [Buildroot] [PATCH] package/wireshark: security bump to v4.4.18
Date: Wed, 19 Aug 2026 11:51:48 +0200 [thread overview]
Message-ID: <87v796l9or.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260818221058.2704747-2-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Wed, 19 Aug 2026 00:10:58 +0200")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> For more information on the version bump, see:
> - https://www.wireshark.org/docs/relnotes/wireshark-4.4.18.html
> At the moment this version fixes a CVE called CVE-2026-xxx that is only
> a placeholder as stated here:
> https://gitlab.com/wireshark/wireshark/-/work_items/21469#note_3696467312
I instead added the list of vulnerabilities and the links to their
details and committed, thanks.
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> package/wireshark/wireshark.hash | 6 +++---
> package/wireshark/wireshark.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
> diff --git a/package/wireshark/wireshark.hash b/package/wireshark/wireshark.hash
> index 917ac47471..3d8fdb6131 100644
> --- a/package/wireshark/wireshark.hash
> +++ b/package/wireshark/wireshark.hash
> @@ -1,6 +1,6 @@
> -# From https://www.wireshark.org/download/src/all-versions/SIGNATURES-4.4.17.txt
> -sha1 d46443d5bbca3580f944f3effcdfcc59e24eb7f4 wireshark-4.4.17.tar.xz
> -sha256 b89a8c60b9282f29be4db91437a6e969e61bc17e8c92ddd980cc38c7304dd772 wireshark-4.4.17.tar.xz
> +# From https://www.wireshark.org/download/src/all-versions/SIGNATURES-4.4.18.txt
> +sha1 482fecbe21a876f53a26bf5beaa5b0ee0ad16e50 wireshark-4.4.18.tar.xz
> +sha256 f77a7939983758383797fed0a34a491f785e541cca397a7a44e9cdd7c6f847c6 wireshark-4.4.18.tar.xz
> # Locally calculated
> sha256 edaef632cbb643e4e7a221717a6c441a4c1a7c918e6e4d56debc3d8739b233f6 COPYING
> diff --git a/package/wireshark/wireshark.mk b/package/wireshark/wireshark.mk
> index 1fd81515c1..c500a49336 100644
> --- a/package/wireshark/wireshark.mk
> +++ b/package/wireshark/wireshark.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -WIRESHARK_VERSION = 4.4.17
> +WIRESHARK_VERSION = 4.4.18
> WIRESHARK_SOURCE = wireshark-$(WIRESHARK_VERSION).tar.xz
> WIRESHARK_SITE = https://www.wireshark.org/download/src/all-versions
> WIRESHARK_LICENSE = wireshark license
> --
> 2.47.3
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-19 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 22:10 [Buildroot] [PATCH] package/udisks: security bump to version 2.11.2 Giulio Benetti
2026-08-18 22:10 ` [Buildroot] [PATCH] package/wireshark: security bump to v4.4.18 Giulio Benetti
2026-08-19 9:51 ` Peter Korsgaard [this message]
2026-08-19 9:51 ` [Buildroot] [PATCH] package/udisks: security bump to version 2.11.2 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=87v796l9or.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=marek.belisko@open-nandra.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