Skip to contentSkip to conversation

zeromq: bump to version 4.3.1

PATCH New Asaf Kahlon 3 participants 3 messages Jan 12, 2019 – Jan 15, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 zeromq: bump to version 4.3.1

Remove the patches as they're already on upstream. As a consequence, no need to autoreconf anymore. Also added license hashes.

---
 ...-serach-for-dladdr-only-on-libunwind.patch | 45 ------------
 ...nclude.m4-check-if-latomic-is-needed.patch | 71 -------------------
 package/zeromq/zeromq.hash                    |  8 ++-
 package/zeromq/zeromq.mk                      |  4 +-
 4 files changed, 6 insertions(+), 122 deletions(-)
 delete mode 100644 package/zeromq/0001-configure.ac-serach-for-dladdr-only-on-libunwind.patch
 delete mode 100644 package/zeromq/0002-acinclude.m4-check-if-latomic-is-needed.patch
package/zeromq/0001-configure.ac-serach-for-dladdr-only-on-libunwind.patch deleted +0 -45
deleted file mode 100644
index 1037a67fe2..0000000000
@@ -1,45 +0,0 @@
-From 194b3836c87f77aca34581656ff99da49813d8c3 Mon Sep 17 00:00:00 2001
-From: Asaf Kahlon <[email protected]>
-Date: Fri, 13 Apr 2018 11:56:46 +0300
-Subject: [PATCH] configure.ac: search for dladdr only on libunwind
-
-The original configure.ac tries to check for dladdr, but it actually needs
-it only in case we have libunwind (which has a another section and checks for it
-too).
-This can fail the build on systems without dynamic linking support.
-Therefore, the dladdr check has to be performed only when checking libunwind.
-
-Signed-off-by: Asaf Kahlon <[email protected]>
-Upstream-status: https://github.com/zeromq/libzmq/commit/c971445025535b9f989ab0b78f5ddd1c026f1878
----
- configure.ac | 7 +------
- 1 file changed, 1 insertion(+), 6 deletions(-)
-
-diff --git a/configure.ac b/configure.ac
-index 216b2bc4..0858a6c1 100644
---- a/configure.ac
-+++ b/configure.ac
-@@ -174,11 +174,6 @@ case "${host_os}" in
-         AC_DEFINE(ZMQ_HAVE_LINUX, 1, [Have Linux OS])
-         libzmq_on_linux="yes"
- 
--        # dladdr/dlopen is in libdl on glibc
--        AC_SEARCH_LIBS([dladdr], [dl dld], [], [
--          AC_MSG_ERROR([unable to find the dladdr() function])
--        ])
--
-         if test "x$libzmq_tipc_support" = "xyes"; then
-             AC_DEFINE(ZMQ_HAVE_TIPC, 1, [Have TIPC support])
-         fi
-@@ -783,7 +778,7 @@ if test "x$enable_libunwind" != "xno"; then
-             AC_DEFINE(HAVE_LIBUNWIND, 1, [The libunwind library is to be used])
-             AC_SUBST([LIBUNWIND_CFLAGS])
-             AC_SUBST([LIBUNWIND_LIBS])
--            AC_CHECK_LIB([dl], [dladdr])
-+            AC_SEARCH_LIBS([dladdr], [dl dld])
-         ],
-         [
-             if test "x$enable_libunwind" = "xyes"; then
--- 
-2.17.0
-
package/zeromq/0002-acinclude.m4-check-if-latomic-is-needed.patch deleted +0 -71

71 lines not on this page · raw message

package/zeromq/zeromq.hash +5 -3
index 86380c0295..5af6a3ff8d 100644
@@ -1,5 +1,7 @@
 # From https://github.com/zeromq/libzmq/releases
-md5  a1c95b34384257e986842f4d006957b8  zeromq-4.2.5.tar.gz
-sha1 1132f839d703486c4ee1cf22f056585dfbb329c2  zeromq-4.2.5.tar.gz
+md5  64cbf3577afdbfda30358bc757a6ac83  zeromq-4.3.1.tar.gz
+sha1 6cce22d830eaf95feff7cab00744df13ad7ab7f3  zeromq-4.3.1.tar.gz
 # Locally computed
-sha256 cc9090ba35713d59bb2f7d7965f877036c49c5558ea0c290b0dcc6f2a17e489f  zeromq-4.2.5.tar.gz
+sha256 bcbabe1e2c7d0eec4ed612e10b94b112dd5f06fcefa994a0c79a45d835cd21eb  zeromq-4.3.1.tar.gz
+sha256 4fd86507c9b486764343065a9e035222869a27b5789efeb4fd93edc85412d7a3  COPYING
+sha256 83f32abe61ee58ffb1b007412c08415168c052501dbf56d7a47aaaac52b03ef6  COPYING.LESSER
package/zeromq/zeromq.mk +1 -3
index 4b25c7d678..da57f8745c 100644
@@ -4,15 +4,13 @@
 #
 ################################################################################
 
-ZEROMQ_VERSION = 4.2.5
+ZEROMQ_VERSION = 4.3.1
 ZEROMQ_SITE = https://github.com/zeromq/libzmq/releases/download/v$(ZEROMQ_VERSION)
 ZEROMQ_INSTALL_STAGING = YES
 ZEROMQ_DEPENDENCIES = util-linux
 ZEROMQ_CONF_OPTS = --without-documentation
 ZEROMQ_LICENSE = LGPL-3.0+ with exceptions
 ZEROMQ_LICENSE_FILES = COPYING COPYING.LESSER
-# 0001-configure.ac-serach-for-dladdr-only-on-libunwind.patch touches configure.ac
-ZEROMQ_AUTORECONF = YES
 
 # Assume these flags are always available. It is true, at least for
 # SOCK_CLOEXEC, since linux v2.6.27.
Signature · 1 line
2.19.1
#1 lore raw

PATCH 1/1 zeromq: bump to version 4.3.1

Hello,

Quoted 5 lines · Asaf Kahlon

Remove the patches as they're already on upstream. As a consequence, no need to autoreconf anymore. Also added license hashes.

Quoted 8 lines
---
 ...-serach-for-dladdr-only-on-libunwind.patch | 45 ------------
 ...nclude.m4-check-if-latomic-is-needed.patch | 71 -------------------
 package/zeromq/zeromq.hash                    |  8 ++-
 package/zeromq/zeromq.mk                      |  4 +-
 4 files changed, 6 insertions(+), 122 deletions(-)
 delete mode 100644 package/zeromq/0001-configure.ac-serach-for-dladdr-only-on-libunwind.patch
 delete mode 100644 package/zeromq/0002-acinclude.m4-check-if-latomic-is-needed.patch

Applied to master, thanks.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

PATCH 1/1 zeromq: bump to version 4.3.1

In reply to Asaf Kahlon
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Asaf" == Asaf Kahlon <[email protected]> writes:

Remove the patches as they're already on upstream. As a consequence, no need to autoreconf anymore. Also added license hashes.

Looking at https://github.com/zeromq/libzmq/releases, I see that this release also fixes security issues:

CVE-2019-6250: A vulnerability has been found that would allow attackers to direct a peer to jump to and execute from an address indicated by the attacker.
This issue has been present since v4.2.0. Older releases are not affected.
NOTE: The attacker needs to know in advance valid addresses in the peer's memory to jump to, so measures like ASLR are effective mitigations.
NOTE: this attack can only take place after authentication, so peers behind CURVE/GSSAPI are not vulnerable to unauthenticated attackers.
See #3351 for more details.

Once more, please mark version bumps that fix security vulnerabilities as such so I don't miss them when backporting to the stable/LTS branches.

Signature · 1 line
Bye, Peter Korsgaard