Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org,  Alexander Dahl <post@lespocky.de>
Subject: Re: [Buildroot] [PATCH 1/1] package/fastd: security bump to version 23
Date: Sun, 05 Oct 2025 15:35:14 +0200	[thread overview]
Message-ID: <87ms65320d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20251004100747.1412268-1-dario.binacchi@amarulasolutions.com> (Dario Binacchi's message of "Sat, 4 Oct 2025 12:07:47 +0200")

>>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:

 > This bump includes the security fix for CVE-2025-24356.
 > Fixes:
 > https://www.cve.org/CVERecord?id=CVE-2025-24356.

 > The COPYRIGHT file was renamed to LICENSE [1]. The hash file was updated
 > because a date was removed [2] and the libmnl version was updated [3].

 > Release notes:
 > https://fastd.readthedocs.io/en/stable/releases/v23.html

 > [1] https://github.com/neocturne/fastd/commit/fa88c739b9afe053905bddc7fbb9c252e290c35d
 > [2] https://github.com/neocturne/fastd/commit/318c944f40c90e048e370b2f75598bfcd79a1790
 > [3] https://github.com/neocturne/fastd/commit/c08a3d59debddf5f99e442d9529a142f04549b50
 > Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>

Committed after updating FASTD_LICENSE_FILES, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-10-05 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-04 10:07 [Buildroot] [PATCH 1/1] package/fastd: security bump to version 23 Dario Binacchi
2025-10-05 13:35 ` Peter Korsgaard [this message]
2025-10-09 14:54 ` Thomas Perale via buildroot

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=87ms65320d.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=post@lespocky.de \
    /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