From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 02/14] curl: upgrade 7.63.0 -> 7.64.0
Date: Thu, 21 Feb 2019 12:41:18 +0000 [thread overview]
Message-ID: <20190221124130.25733-2-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20190221124130.25733-1-richard.purdie@linuxfoundation.org>
The license checksum changed as the copyright years changed.
Fixes:
- CVE-2018-16890: NTLM type-2 out-of-bounds buffer read
- CVE-2019-3822: NTLMv2 type-3 header stack buffer overflow
- CVE-2019-3823: SMTP end-of-response out-of-bounds read
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../recipes-support/curl/{curl_7.63.0.bb => curl_7.64.0.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-support/curl/{curl_7.63.0.bb => curl_7.64.0.bb} (93%)
diff --git a/meta/recipes-support/curl/curl_7.63.0.bb b/meta/recipes-support/curl/curl_7.64.0.bb
similarity index 93%
rename from meta/recipes-support/curl/curl_7.63.0.bb
rename to meta/recipes-support/curl/curl_7.64.0.bb
index f7557a2f46d..a1b5e7d5797 100644
--- a/meta/recipes-support/curl/curl_7.63.0.bb
+++ b/meta/recipes-support/curl/curl_7.64.0.bb
@@ -3,14 +3,14 @@ HOMEPAGE = "http://curl.haxx.se/"
BUGTRACKER = "http://curl.haxx.se/mail/list.cgi?list=curl-tracker"
SECTION = "console/network"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://COPYING;md5=ef889a37a5a874490ac7ce116396f29a"
+LIC_FILES_CHKSUM = "file://COPYING;md5=be5d9e1419c4363f4b32037a2d3b7ffa"
SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
file://0001-replace-krb5-config-with-pkg-config.patch \
"
-SRC_URI[md5sum] = "0a6c1e993bd5102bc52fc89900542644"
-SRC_URI[sha256sum] = "9bab7ed4ecff77020a312d84cc5fb7eb02d58419d218f267477a724a17fd8dd8"
+SRC_URI[md5sum] = "d0bcc586873cfef08b4b9594e5395a33"
+SRC_URI[sha256sum] = "d573ba1c2d1cf9d8533fadcce480d778417964e8d04ccddcc76e591d544cf2eb"
CVE_PRODUCT = "curl libcurl"
inherit autotools pkgconfig binconfig multilib_header
--
2.20.1
next prev parent reply other threads:[~2019-02-21 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 12:41 [PATCH 01/14] blktool: upgrade 4-7 -> 4-7.1 Richard Purdie
2019-02-21 12:41 ` Richard Purdie [this message]
2019-02-21 12:41 ` [PATCH 03/14] gnupg: upgrade 2.2.12 -> 2.2.13 Richard Purdie
2019-02-21 12:41 ` [PATCH 04/14] gst-examples: upgrade to latest revision Richard Purdie
2019-02-21 12:41 ` [PATCH 05/14] less: upgrade 530 -> 549 Richard Purdie
2019-02-21 12:41 ` [PATCH 06/14] libassuan: upgrade 2.5.2 -> 2.5.3 Richard Purdie
2019-02-21 12:41 ` [PATCH 07/14] libxau: upgrade 1.0.8 -> 1.0.9 Richard Purdie
2019-02-21 12:41 ` [PATCH 08/14] netbase: upgrade 5.5 -> 5.6 Richard Purdie
2019-02-21 12:41 ` [PATCH 09/14] pkgconf: upgrade 1.5.3 -> 1.6.0 Richard Purdie
2019-02-21 12:41 ` [PATCH 10/14] readline: upgrade 7.0 -> 8.0 Richard Purdie
2019-02-21 12:41 ` [PATCH 11/14] sbc: upgrade 1.3 -> 1.4 Richard Purdie
2019-02-21 12:41 ` [PATCH 12/14] xf86-input-libinput: upgrade 0.28.1 -> 0.28.2 Richard Purdie
2019-02-21 12:41 ` [PATCH 13/14] xkeyboard-config: upgrade 2.25 -> 2.26 Richard Purdie
2019-02-21 12:41 ` [PATCH 14/14] gnu-config: upgrade to 20181128 revision Richard Purdie
2019-02-22 15:14 ` [PATCH 01/14] blktool: upgrade 4-7 -> 4-7.1 Adrian Bunk
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=20190221124130.25733-2-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox