From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/2] Pull request (cover letter only)
Date: Tue, 4 Oct 2022 09:31:28 -1000 [thread overview]
Message-ID: <cover.1664911788.git.steve@sakoman.com> (raw)
This should be the final pull request for the upcoming 3.1.20 build.
The following changes since commit 7a08f2ae1c12e3511b409c4535d2eab83a27b64a:
create-pull-request: don't switch the git remote protocol to git:// (2022-09-29 06:45:30 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Mathieu Dubois-Briand (1):
bind: Fix CVEs 2022-2795, 2022-38177, 2022-38178
Paul Barker (1):
licenses: Handle newer SPDX license names
meta/conf/licenses.conf | 7 ++
.../bind/bind/CVE-2022-2795.patch | 67 +++++++++++++++++++
.../bind/bind/CVE-2022-38177.patch | 31 +++++++++
.../bind/bind/CVE-2022-38178.patch | 33 +++++++++
.../recipes-connectivity/bind/bind_9.11.37.bb | 3 +
5 files changed, 141 insertions(+)
create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2022-2795.patch
create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2022-38177.patch
create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2022-38178.patch
--
2.25.1
next reply other threads:[~2022-10-04 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 19:31 Steve Sakoman [this message]
2022-10-05 3:30 ` [OE-core][dunfell 0/2] Pull request (cover letter only) Tim Orling
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 15:27 Steve Sakoman
2020-11-03 3:07 Steve Sakoman
2020-10-09 0:17 Steve Sakoman
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=cover.1664911788.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=openembedded-core@lists.openembedded.org \
/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.