|
1 | 1 | 0MQ version 4.3.2 stable, released on 20xx/xx/xx |
2 | 2 | ================================================ |
3 | 3 |
|
| 4 | +* CVE-2019-13132: a remote, unauthenticated client connecting to a |
| 5 | + libzmq application, running with a socket listening with CURVE |
| 6 | + encryption/authentication enabled, may cause a stack overflow and |
| 7 | + overwrite the stack with arbitrary data, due to a buffer overflow in |
| 8 | + the library. Users running public servers with the above configuration |
| 9 | + are highly encouraged to upgrade as soon as possible, as there are no |
| 10 | + known mitigations. All versions from 4.0.0 and upwards are affected. |
| 11 | + Thank you Fang-Pen Lin for finding the issue and reporting it! |
| 12 | + |
| 13 | +* New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_versioned API that supports |
| 14 | + a versioned monitoring events protocol as a parameter. Passing 1 results in |
| 15 | + the same behaviour as zmq_socket_monitor. |
| 16 | + Version 2 of the events protocol allows new events, new metadata, different |
| 17 | + socket types for the monitors and more. It is described in details in |
| 18 | + doc/zmq_socket_monitor_versioned.txt |
| 19 | + |
| 20 | +* New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_pipes_stats that triggers |
| 21 | + a new ZMQ_EVENT_PIPES_STATS to be delivered via zmq_socket_monitor_versioned |
| 22 | + v2 API, which contains the current status of all the queues owned by the |
| 23 | + monitored socket. See doc/zmq_socket_monitor_versioned.txt for details. |
| 24 | + |
| 25 | +* New DRAFT (see NEWS for 4.2.0) zmq_poller_fd that returns the FD of a thread |
| 26 | + safe socket. See doc/zmq_poller.txt for details. |
| 27 | + |
| 28 | +* New DRAFT (see NEWS for 4.2.0) socket options: |
| 29 | + - ZMQ_XPUB_MANUAL_LAST_VALUE is similar to ZMQ_XPUB_MANUAL but allows to avoid |
| 30 | + duplicates when using last value caching. |
| 31 | + - ZMQ_SOCKS_USERNAME and ZMQ_SOCKS_PASSWORD that implement SOCKS5 proxy |
| 32 | + authentication. |
| 33 | + See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details. |
| 34 | + |
| 35 | +* Implemented background thread names for Windows, when the Visual Studio |
| 36 | + debugger is being used. |
| 37 | + |
| 38 | +* Fixed #3358 - test_security_zap failing due to SIGBUS on SPARC64, hard-coded |
| 39 | + IPC socket binds in tests cause race conditions |
| 40 | + |
| 41 | +* Fixed #3361 - enabling GSSAPI support (when using autools) does not work due |
| 42 | + to regression introduced in 4.2.3 |
| 43 | + |
| 44 | +* Fixed #3362 - remove documentation for ZMQ_THREAD_PRIORITY context option |
| 45 | + getter, it's not implemented |
| 46 | + |
| 47 | +* Fixed #3363 - tests fail to build due to stricter compiler printf validation |
| 48 | + in new versions of GCC |
| 49 | + |
| 50 | +* Fixed #3367 - try to infer cacheline size at build time, first with |
| 51 | + getconf LEVEL1_DCACHE_LINESIZE, and then by reading |
| 52 | + /sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size |
| 53 | + (autoconf only), and only then falling back to the previous |
| 54 | + default of 64 bytes. Avoids false sharing on POWER and s390x. |
| 55 | + Import ax_func_posix_memalign.m4 as a more reliable check for |
| 56 | + posix_memalign presence on some unix platforms. |
| 57 | + Prefer c++11 atomic primitives to compiler intrinsics, when |
| 58 | + both are available, as the former is more reliable. |
| 59 | + Set test_pair_ipc and test_rebind_ipc to XFAIL on GNU/Hurd due |
| 60 | + to non-functioning getsockname on AF_UNIX. |
| 61 | + |
| 62 | +* Fixed #3370 - Make queue length and HWM state observable |
| 63 | + |
| 64 | +* Fixed #3373 - performance regression in zmq_poll on CentOS 6/7 |
| 65 | + |
| 66 | +* Fixed #3375 - assign names to all pthreads created by the library to ease |
| 67 | + debugging |
| 68 | + |
| 69 | +* Fixed #3376 - assigned random TIPC port is not returned by ZMQ_LAST_ENDPOINT |
| 70 | + |
| 71 | +* Fixed #3385 - TCP port in ZMQ_LAST_ENDPOINT depends on global locale |
| 72 | + |
| 73 | +* Fixed #3404 - use std::condition_variable_any when possible |
| 74 | + |
| 75 | +* Fixed #3436 - reconnect interval exponential backoff and may lead to integer |
| 76 | + overflows |
| 77 | + |
| 78 | +* Fixed #3440 - improve zmq_proxy performance by batching of up to 1000 |
| 79 | + consecutive messages (if any) and add perf/proxy_thr tool |
| 80 | + |
| 81 | +* Fixed #3451 - fix support of /dev/poll on Solaris |
| 82 | + |
| 83 | +* Fixed #3452 - strnlen may not be available |
| 84 | + |
| 85 | +* Fixed #1462 - test failure in test_filter_ipc due to invalid system groups |
| 86 | + |
| 87 | +* Fixed #3269 - Boost.ASIO integration stopped working with v4.3.0 |
| 88 | + |
| 89 | +* Fixed #3479 - ZeroMQ does not build for QNX 6.6 with CMake |
| 90 | + |
| 91 | +* Fixed #3481 - add <ios> include to fix uClibc++ compilation |
| 92 | + |
| 93 | +* Fixed #3491 - build broken on Fedora 30 |
| 94 | + |
| 95 | +* Fixed #3494 - ZeroMQConfig.cmake fails if shared libraries are not built |
| 96 | + |
| 97 | +* Fixed #3498 - syntax error on Windows related to socket descriptor type |
| 98 | + |
| 99 | +* Fixed #3500 - PLAIN HELLO message incorrectly uses WELCOME literal, regression |
| 100 | + introduced in 4.3.0 |
| 101 | + |
| 102 | +* Fixed #3517 - configure errors because of syntax errors in the use of test |
| 103 | + shell command |
| 104 | + |
| 105 | +* Fixed #3521 - document how to achieve high performance with the PGM transport |
| 106 | + |
| 107 | +* Fixed #3526 - failure case behavior unclear in zmq_msg_send documentation |
| 108 | + |
| 109 | +* Fixed #3537 - fix build on z/OS by using pthread_equal instead of comparing |
| 110 | + variables directly |
| 111 | + |
| 112 | +* Fixed #3546 - CMake links with librt on MinGW which is not available |
| 113 | + |
| 114 | +* Many coding style, duplication, testing and static analysis improvements. |
| 115 | + |
| 116 | + |
4 | 117 | 0MQ version 4.3.1 stable, released on 2019/01/12 |
5 | 118 | ================================================ |
6 | 119 |
|
|
0 commit comments