Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/ntpsec: security bump version to 1.2.6
Date: Wed, 28 Oct 2026 20:21:46 +0100	[thread overview]
Message-ID: <f701452e751c19574c6a9ec8eeea814a@free.fr> (raw)
In-Reply-To: <20261027194638.2165377-1-ps.report@gmx.net>

On 27/10/2026 20:46, Peter Seiderer via buildroot wrote:
> - bump version to 1.2.6 (for details see [1])
> - fixes CVE-2026-102486, CVE-2026-102483, CVE-2026-102484, 
> CVE-2026-102485
> 
> [1] https://lists.ntpsec.org/pipermail/devel/2026-October/011062.html
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-28 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 19:46 [Buildroot] [PATCH v1] package/ntpsec: security bump version to 1.2.6 Peter Seiderer via buildroot
2026-10-28 19:21 ` Julien Olivain via buildroot [this message]

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=f701452e751c19574c6a9ec8eeea814a@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=ps.report@gmx.net \
    /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