From: <jackie.huang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-networking][PATCH] quagga: update to 1.2.4
Date: Mon, 9 Apr 2018 11:30:50 +0800 [thread overview]
Message-ID: <20180409033050.27114-1-jackie.huang@windriver.com> (raw)
From: Jackie Huang <jackie.huang@windriver.com>
Update to 1.2.4 to fix significant BGP security issues:
* https://www.quagga.net/security/Quagga-2018-0543.txt(CVE-2018-5378)
* https://www.quagga.net/security/Quagga-2018-1114.txt(CVE-2018-5379)
* https://www.quagga.net/security/Quagga-2018-1550.txt(CVE-2018-5380)
* https://www.quagga.net/security/Quagga-2018-1975.txt(CVE-2018-5381)
Detail release notes:
http://savannah.nongnu.org/forum/forum.php?forum_id=9099
http://savannah.nongnu.org/forum/forum.php?forum_id=9095
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
---
.../recipes-protocols/quagga/{quagga_1.2.2.bb => quagga_1.2.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-networking/recipes-protocols/quagga/{quagga_1.2.2.bb => quagga_1.2.4.bb} (12%)
diff --git a/meta-networking/recipes-protocols/quagga/quagga_1.2.2.bb b/meta-networking/recipes-protocols/quagga/quagga_1.2.4.bb
similarity index 12%
rename from meta-networking/recipes-protocols/quagga/quagga_1.2.2.bb
rename to meta-networking/recipes-protocols/quagga/quagga_1.2.4.bb
index 653f46b36..a7697a1ae 100644
--- a/meta-networking/recipes-protocols/quagga/quagga_1.2.2.bb
+++ b/meta-networking/recipes-protocols/quagga/quagga_1.2.4.bb
@@ -1,4 +1,4 @@
require quagga.inc
-SRC_URI[md5sum] = "e84be2938c26c0c872792090f1a6a866"
-SRC_URI[sha256sum] = "522e22f2beee64e3f0c2cde3d0155f3b8103f4f6fc8abef92cb40bc3a4cc2931"
+SRC_URI[md5sum] = "eced21b054d71c9e1b7c6ac43286a166"
+SRC_URI[sha256sum] = "e364c082c3309910e1eb7b068bf39ee298e2f2f3f31a6431a5c115193bd653d3"
--
2.11.0
reply other threads:[~2018-04-09 3:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180409033050.27114-1-jackie.huang@windriver.com \
--to=jackie.huang@windriver.com \
--cc=openembedded-devel@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.