All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnpupnp: bump to version 4.1.3
Date: Mon, 26 Apr 2021 16:56:31 +0200	[thread overview]
Message-ID: <8735vdjdr4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87czuhcg9c.fsf@tarshish> (Baruch Siach's message of "Mon, 26 Apr 2021 16:44:15 +0300")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > Hi Peter,
 > On Mon, Apr 26 2021, Peter Korsgaard wrote:

 >>>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
 >> 
 >> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
 >> 
 >> Committed to 2021.02.x, thanks.

 > Not in 2021.02.x as of commit 2960953b0ab6de.

No indeed, I sent the mail too soon. I misremembered what version we
have in 2021.02.x.

 > What is the reason to commit to 2021.02.x?

 > Master branch commit adea5b316e27a is the 4.1.4 bump which includes a
 > security fix.

Exactly because of the 4.1.4 security fix. The changelog is very light
on detail about what got fixed and what versions are affected, but it is
presumably this commit:

https://framagit.org/medoc92/npupnp/-/commit/90a4ab27dcec97d85168204ac8aed98f9f50e184

I'll take a closer look tonight and then update 2021.02.x to 4.1.4.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2021-04-26 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  8:04 [Buildroot] [PATCH 1/1] package/libnpupnp: bump to version 4.1.3 Jörg Krause
2021-04-19 21:45 ` Thomas Petazzoni
2021-04-26 12:31 ` Peter Korsgaard
2021-04-26 13:44   ` Baruch Siach
2021-04-26 14:56     ` Peter Korsgaard [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=8735vdjdr4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.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 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.