Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

libzmq5-4.3.5-1.3 RPM for armv7hl

From OpenSuSE Ports Tumbleweed for armv7hl

Name: libzmq5 Distribution: openSUSE Tumbleweed
Version: 4.3.5 Vendor: openSUSE
Release: 1.3 Build date: Sat Feb 10 02:52:01 2024
Group: Productivity/Networking/Web/Servers Build host: i01-armsrv1
Size: 489256 Source RPM: zeromq-4.3.5-1.3.src.rpm
Summary: Shared Library for ZeroMQ
The ZeroMQ messaging kernel is a library extending the standard
socket interfaces with an abstraction of asynchronous message queues,
multiple messaging patterns, message filtering (subscriptions) and
seamless access to multiple transport protocols.

This package holds the shared library part of the ZeroMQ package.






* Tue Oct 24 2023 Adam Majer <>
  - update to 4.3.5:
    * Relicensing from LGPL-3.0+ (with custom exceptions) to MPL-2.0 is now complete.
      libzmq is now distributed under the Mozilla Public License 2.0. Relicensing
      grants have been collected from all relevant authors, and some functionality
      has been clean-room reimplemented where that was not possible. In layman terms,
      the new license provides the same rights and obligations as before. Source
      files are now tagged using the SPDX license identifier format.
      Details of the relicensing process can be seen at: #2376
      Relicensing grants have been archived at:
      A special thanks to everybody who helped with this long and difficult task,
      with the process, the reimplementations, the collections and everything else.
    * New DRAFT (see NEWS for 4.2.0) socket options:
      ZMQ_BUSY_POLL will set the SO_BUSY_POLL socket option on the underlying
      sockets, if it is supported.
      ZMQ_HICCUP_MSG will send a message when the peer has been disconnected.
      ZMQ_XSUB_VERBOSE_UNSUBSCRIBE will configure a socket to pass all
      unsubscription messages, including duplicated ones.
      ZMQ_TOPICS_COUNT will return the number of subscribed topics on a
      PUB/SUB socket.
      ZMQ_NORM_NUM_AUTOPARITY and ZMQ_NORM_PUSH to control various aspect of
      NORM sockets.
      See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.
    * New DRAFT (see NEWS for 4.2.0) zmq_ppoll APIs was added that differs from
      zmq_poll in the same way that ppoll differs from poll.
      See doc/zmq_ppoll.txt for details.
    * Various bug fixes and performance improvements.
  - qemu-user.patch: upstreamed, removed
* Mon Jan 23 2023 Andreas Schwab <>
  - qemu-user.patch: Fix build with qemu linux-user emulation
* Mon Aug 15 2022 Dirk Müller <>
  - drop xmlto and asciidoc buildrequires, these are only needed
    for non-release builds which do not ship with prebuilt docs
* Mon Jun 28 2021 Matej Cepl <>
  - Explicit BR on python is not necessary.
* Sun Jan 24 2021 Dirk Müller <>
  - update to 4.3.4:
    * ZMQ_PRIORITY will set the SO_PRIORITY socket option on the underlying
      sockets. Only supported on Linux.
    * Fixed compilation errors on kFreeBSD and GNU/Hurd
    * Fixed excessive amount of socket files left behind in Windows TMP
    * Fixed regression that breaks using IPv6 link-local addresses on Linux
    * Fixed compilation errors on Android
    * Fixed compilation error with ulibc and libbsd
    * Fixed stack overflow on Windows x64
    * Fixed various compilation errors on Windows ARM 32bit
    * Fixed various compilation warnings with XCode
    * Fixed return value of zmq_ctx_get changed unintentionally
* Mon Sep 07 2020 Adam Majer <>
  - New upstream version 4.3.3:
    * Denial-of-Service on CURVE/ZAP-protected servers by
      unauthenticated clients. (CVE-2020-15166, bsc#1176116)
      If a raw TCP socket is opened and connected to an endpoint that is fully
      configured with CURVE/ZAP, legitimate clients will not be able to exchange
      any message. Handshakes complete successfully, and messages are delivered to
      the library, but the server application never receives them.
      For more information see the security advisory:
    * Stack overflow on server running PUB/XPUB socket (CURVE disabled).
      The PUB/XPUB subscription store (mtrie) is traversed using recursive
      function calls. In the remove (unsubscription) case, the recursive calls are
      NOT tail calls, so even with optimizations the stack grows linearly with the
      length of a subscription topic. Topics are under the control of remote
      clients - they can send a subscription to arbitrary length topics. An
      attacker can thus cause a server to create an mtrie sufficiently large such
      that, when unsubscribing, traversal will cause a stack overflow. (bsc#1176258)
      For more information see the security advisory:
    * Memory leak in PUB server induced by malicious client(s) without CURVE/ZAP.
      Messages with metadata are never processed by PUB sockets, but the metadata
      is kept referenced in the PUB object and never freed. (bsc#1176257)
      For more information see the security advisory:
    * Memory leak in client induced by malicious server(s) without CURVE/ZAP.
      When a pipe processes a delimiter and is already not in active state but
      still has an unfinished message, the message is leaked. (bsc#1176259)
      For more information see the security advisory:
    * Heap overflow when receiving malformed ZMTP v1 packets (CURVE disabled).
      By crafting a packet which is not valid ZMTP v2/v3, and which has two
      messages larger than 8192 bytes, the decoder can be tricked into changing
      the recorded size of the 8192 bytes static buffer, which then gets overflown
      by the next message. The content that gets written in the overflown memory
      is entirely decided by the sender. (bsc#1176256)
      For more information see the security advisory:
    For complete list of changes, see
* Tue Jul 09 2019 Vítězslav Čížek <>
  - New upstream version 4.3.2:
    * CVE-2019-13132: a remote, unauthenticated client connecting to a
      libzmq application, running with a socket listening with CURVE
      encryption/authentication enabled, may cause a stack overflow and
      overwrite the stack with arbitrary data, due to a buffer overflow in
      the library. Users running public servers with the above configuration
      are highly encouraged to upgrade as soon as possible, as there are no
      known mitigations. (bsc#1140255)
    * New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_versioned API that supports
      a versioned monitoring events protocol as a parameter. Passing 1 results in
      the same behaviour as zmq_socket_monitor.
    * New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_pipes_stats that triggers
      a new ZMQ_EVENT_PIPES_STATS to be delivered via zmq_socket_monitor_versioned
      v2 API, which contains the current status of all the queues owned by the
      monitored socket. See doc/zmq_socket_monitor_versioned.txt for details.
    * New DRAFT (see NEWS for 4.2.0) zmq_poller_fd that returns the FD of a thread
      safe socket.
    * New DRAFT (see NEWS for 4.2.0) socket options:
      ZMQ_XPUB_MANUAL_LAST_VALUE is similar to ZMQ_XPUB_MANUAL but allows to avoid
      duplicates when using last value caching.
      ZMQ_SOCKS_USERNAME and ZMQ_SOCKS_PASSWORD that implement SOCKS5 proxy
  - For complete set of changes, see
* Mon Jan 14 2019
  - New upstream version 4.3.1:
    * 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. (bsc#1121717)
    * fixed race condition in ZMQ_PUSH when quickly disconnecting and
      reconnecting causes last part of multi-part message to get
      "stuck" and resent by mistake to the new socket.
    For complete set of changes, see,
* Tue Jul 10 2018
  - Add baselibs.conf: build libzmq5-32bit, as it is a required
    dependency to libavfilter7-32bit (i.e ffmpeg 4).
* Mon Mar 26 2018
  - New upstream version 4.2.5:
    * fix backward-incompatible change in the NULL auth
      mechanism that slipped in 4.2.3 and made connections
      with a ZAP domain set on a socket but without a working
      ZAP handler fail. See ZMQ_ZAP_ENFORCE_DOMAIN
    * clarify in zmq_close manpage that the operation will
      complete asynchronously.



Generated by rpm2html 1.8.1

Fabrice Bellet, Tue May 28 00:16:47 2024