From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/go: security bump to 1.17.5
Date: Sat, 15 Jan 2022 11:56:04 +0100 [thread overview]
Message-ID: <8735lp5ku3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+h8R2o_bHkD2g+mJGsxMbNfDSSiOXj3wn_uhC+90xVeT-ceDA@mail.gmail.com> (Christian Stewart via buildroot's message of "Thu, 6 Jan 2022 13:39:35 -0800")
>>>>> "Christian" == Christian Stewart via buildroot <buildroot@buildroot.org> writes:
> Hi maintainers, all,
> Currently 2021.11.x branch is at version 1.17.3 which is vulnerable to:
> - CVE-2021-44716
> - CVE-2021-44717
> Is it currently policy to backport security patches?
> Similarly the 2021.02.x LTS branch is at 1.16.10, when the security
> fixes landed in 1.16.12.
> I've just submitted 1.17.6 to the list and will submit 1.16.12 for
> 2021.02.x as well.
Committed to 2021.11.x, thanks. Sorry for the delay.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-15 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 9:01 [Buildroot] [PATCH 1/1] package/go: security bump to 1.17.5 Christian Stewart via buildroot
2021-12-12 15:13 ` Arnout Vandecappelle
2021-12-12 16:00 ` Yann E. MORIN
2022-01-06 21:39 ` Christian Stewart via buildroot
2022-01-06 21:54 ` Arnout Vandecappelle
2022-01-15 10: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=8735lp5ku3.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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.