From DESCR:
This Python module allows you to create TCP connections through a SOCKS proxy
without any special effort.
This is needed as one of the dependencies of py-gsutil, as noted in
PR pkg/52941.
1.14.30
api-change:budgets: Update budgets command to latest version
1.14.29
api-change:glue: Update glue command to latest version
api-change:transcribe: Update transcribe command to latest version
1.14.28
api-change:sagemaker: Update sagemaker command to latest version
1.14.27
api-change:ec2: Update ec2 command to latest version
api-change:autoscaling-plans: Update autoscaling-plans command to latest version
1.14.26
api-change:application-autoscaling: Update application-autoscaling command to latest version
api-change:rds: Update rds command to latest version
api-change:autoscaling-plans: Update autoscaling-plans command to latest version
1.14.25
api-change:lambda: Update lambda command to latest version
1.14.24
api-change:glue: Update glue command to latest version
1.14.23
api-change:elb: Update elb command to latest version
api-change:elbv2: Update elbv2 command to latest version
api-change:ssm: Update ssm command to latest version
api-change:rds: Update rds command to latest version
1.14.22
api-change:kms: Update kms command to latest version
1.14.21
api-change:ds: Update ds command to latest version
1.14.20
api-change:discovery: Update discovery command to latest version
api-change:codedeploy: Update codedeploy command to latest version
api-change:route53: Update route53 command to latest version
1.14.19
api-change:snowball: Update snowball command to latest version
api-change:ssm: Update ssm command to latest version
api-change:inspector: Update inspector command to latest version
1.14.18
api-change:rds: Update rds command to latest version
1.14.17
api-change:workspaces: Update workspaces command to latest version
1.14.16
api-change:ecs: Update ecs command to latest version
api-change:ec2: Update ec2 command to latest version
api-change:sagemaker: Update sagemaker command to latest version
api-change:inspector: Update inspector command to latest version
1.14.15
api-change:ec2: Update ec2 command to latest version
api-change:kinesisanalytics: Update kinesisanalytics command to latest version
api-change:codebuild: Update codebuild command to latest version
1.14.14
api-change:config: Update config command to latest version
api-change:iot: Update iot command to latest version
1.5.20
======
- api-change:``budgets``: [``botocore``] Update budgets client to
latest version
1.5.19
======
- api-change:``glue``: [``botocore``] Update glue client to latest
version
- api-change:``transcribe``: [``botocore``] Update transcribe client
to latest version
1.5.18
======
- api-change:``sagemaker``: [``botocore``] Update sagemaker client to
latest version
1.5.17
======
- api-change:``ec2``: [``botocore``] Update ec2 client to latest
version
- api-change:``autoscaling-plans``: [``botocore``] Update
autoscaling-plans client to latest version
1.5.16
======
- api-change:``application-autoscaling``: [``botocore``] Update
application-autoscaling client to latest version
- api-change:``autoscaling-plans``: [``botocore``] Update
autoscaling-plans client to latest version
- api-change:``rds``: [``botocore``] Update rds client to latest
version
1.5.15
======
- api-change:``lambda``: [``botocore``] Update lambda client to latest
version
- enhancement:cloudformation get_template template body ordering:
[``botocore``] fixesboto/boto3#1378
1.5.14
======
- api-change:``glue``: [``botocore``] Update glue client to latest
version
1.5.13
======
- api-change:``ssm``: [``botocore``] Update ssm client to latest
version
- api-change:``elbv2``: [``botocore``] Update elbv2 client to latest
version
- api-change:``rds``: [``botocore``] Update rds client to latest
version
- api-change:``elb``: [``botocore``] Update elb client to latest
version
1.5.12
======
- api-change:``kms``: [``botocore``] Update kms client to latest
version
1.5.11
======
- api-change:``ds``: [``botocore``] Update ds client to latest version
1.5.10
======
- api-change:``route53``: [``botocore``] Update route53 client to
latest version
- api-change:``discovery``: [``botocore``] Update discovery client to
latest version
- api-change:``codedeploy``: [``botocore``] Update codedeploy client
to latest version
1.5.9
=====
- api-change:``ssm``: [``botocore``] Update ssm client to latest
version
- api-change:``inspector``: [``botocore``] Update inspector client to
latest version
- api-change:``snowball``: [``botocore``] Update snowball client to
latest version
1.5.8
=====
- api-change:``rds``: [``botocore``] Update rds client to latest
version
1.5.7
=====
- api-change:``workspaces``: [``botocore``] Update workspaces client
to latest version
1.5.6
=====
- api-change:``ecs``: [``botocore``] Update ecs client to latest
version
- api-change:``ec2``: [``botocore``] Update ec2 client to latest
version
- api-change:``inspector``: [``botocore``] Update inspector client to
latest version
- api-change:``sagemaker``: [``botocore``] Update sagemaker client to
latest version
1.5.5
=====
- api-change:``ec2``: [``botocore``] Update ec2 client to latest
version
- enhancement:Paginator: [``botocore``] Added paginator support for
lambda list aliases operation.
- api-change:``kinesisanalytics``: [``botocore``] Update
kinesisanalytics client to latest version
- api-change:``codebuild``: [``botocore``] Update codebuild client to
latest version
1.5.4
=====
- api-change:``iot``: [``botocore``] Update iot client to latest
version
- api-change:``config``: [``botocore``] Update config client to latest
version
1.8.34
======
- api-change:``budgets``: Update budgets client to latest version
1.8.33
======
- api-change:``glue``: Update glue client to latest version
- api-change:``transcribe``: Update transcribe client to latest
version
1.8.32
======
- api-change:``sagemaker``: Update sagemaker client to latest version
1.8.31
======
- api-change:``ec2``: Update ec2 client to latest version
- api-change:``autoscaling-plans``: Update autoscaling-plans client to
latest version
1.8.30
======
- api-change:``application-autoscaling``: Update
application-autoscaling client to latest version
- api-change:``autoscaling-plans``: Update autoscaling-plans client to
latest version
- api-change:``rds``: Update rds client to latest version
1.8.29
======
- api-change:``lambda``: Update lambda client to latest version
- enhancement:cloudformation get_template template body ordering:
fixesboto/boto3#1378
1.8.28
======
- api-change:``glue``: Update glue client to latest version
1.8.27
======
- api-change:``ssm``: Update ssm client to latest version
- api-change:``elbv2``: Update elbv2 client to latest version
- api-change:``rds``: Update rds client to latest version
- api-change:``elb``: Update elb client to latest version
1.8.26
======
- api-change:``kms``: Update kms client to latest version
1.8.25
======
- api-change:``ds``: Update ds client to latest version
1.8.24
======
- api-change:``route53``: Update route53 client to latest version
- api-change:``discovery``: Update discovery client to latest version
- api-change:``codedeploy``: Update codedeploy client to latest
version
1.8.23
======
- api-change:``ssm``: Update ssm client to latest version
- api-change:``inspector``: Update inspector client to latest version
- api-change:``snowball``: Update snowball client to latest version
1.8.22
======
- api-change:``rds``: Update rds client to latest version
1.8.21
======
- api-change:``workspaces``: Update workspaces client to latest
version
1.8.20
======
- api-change:``ecs``: Update ecs client to latest version
- api-change:``ec2``: Update ec2 client to latest version
- api-change:``inspector``: Update inspector client to latest version
- api-change:``sagemaker``: Update sagemaker client to latest version
1.8.19
======
- api-change:``ec2``: Update ec2 client to latest version
- enhancement:Paginator: Added paginator support for lambda list
aliases operation.
- api-change:``kinesisanalytics``: Update kinesisanalytics client to
latest version
- api-change:``codebuild``: Update codebuild client to latest version
1.8.18
======
- api-change:``iot``: Update iot client to latest version
- api-change:``config``: Update config client to latest version
Improvements
- Don't process records for another class than IN
Bug Fixes
- Correctly handle ancestor delegation NSEC{,3} for children.
(CVE-2018-1000003)
- Fix the computation of the closest encloser for positive answers.
- Pass the correct buffer size to arecvfrom().
- Fix to make primeHints threadsafe, otherwise there's a small chance
on startup that the root-server IPs will be incorrect.
- Don't validate signature for "glue" CNAME, since anything else than
the initial CNAME can't be considered authoritative.
Release Notes for BIND Version 9.9.11-P1
Introduction
This document summarizes changes since BIND 9.9.11.
BIND 9.9.11-P1 addresses the security issue described in CVE-2017-3145.
Download
The latest versions of BIND 9 software can always be found at
http://www.isc.org/downloads/. There you will find additional
information about each release, source code, and pre-compiled versions
for Microsoft Windows operating systems.
New DNSSEC Root Key
ICANN is in the process of introducing a new Key Signing Key (KSK) for
the global root zone. BIND has multiple methods for managing DNSSEC
trust anchors, with somewhat different behaviors. If the root key is
configured using the managed-keys statement, or if the pre-configured
root key is enabled by using dnssec-validation auto, then BIND can keep
keys up to date automatically. Servers configured in this way should
have begun the process of rolling to the new key when it was published
in the root zone in July 2017. However, keys configured using the
trusted-keys statement are not automatically maintained. If your server
is performing DNSSEC validation and is configured using trusted-keys,
you are advised to change your configuration before the root zone
begins signing with the new KSK. This is currently scheduled for
October 11, 2017.
This release includes an updated version of the bind.keys file
containing the new root key. This file can also be downloaded from
https://www.isc.org/bind-keys .
Windows XP No Longer Supported
As of BIND 9.9.11, Windows XP is no longer a supported platform for
BIND, and Windows XP binaries are no longer available for download from
ISC.
Security Fixes
* Addresses could be referenced after being freed during resolver
processing, causing an assertion failure. The chances of this
happening were remote, but the introduction of a delay in
resolution increased them. (The delay will be addressed in an
upcoming maintenance release.) This bug is disclosed in
CVE-2017-3145. [RT #46839]
* An error in TSIG handling could permit unauthorized zone transfers
or zone updates. These flaws are disclosed in CVE-2017-3142 and
CVE-2017-3143. [RT #45383]
* The BIND installer on Windows used an unquoted service path, which
can enable privilege escalation. This flaw is disclosed in
CVE-2017-3141. [RT #45229]
* With certain RPZ configurations, a response with TTL 0 could cause
named to go into an infinite query loop. This flaw is disclosed in
CVE-2017-3140. [RT #45181]
Feature Changes
* Threads in named are now set to human-readable names to assist
debugging on operating systems that support that. Threads will have
names such as "isc-timer", "isc-sockmgr", "isc-worker0001", and so
on. This will affect the reporting of subsidiary thread names in ps
and top, but not the main thread. [RT #43234]
* DiG now warns about .local queries which are reserved for Multicast
DNS. [RT #44783]
Bug Fixes
* Fixed a bug that was introduced in an earlier development release
which caused multi-packet AXFR and IXFR messages to fail validation
if not all packets contained TSIG records; this caused
interoperability problems with some other DNS implementations. [RT
#45509]
* Semicolons are no longer escaped when printing CAA and URI records.
This may break applications that depend on the presence of the
backslash before the semicolon. [RT #45216]
* AD could be set on truncated answer with no records present in the
answer and authority sections. [RT #45140]
End of Life
BIND 9.9 (Extended Support Version) will be supported until at least
June, 2018. https://www.isc.org/downloads/software-support-policy/
Release Notes for BIND Version 9.10.6-P1
Introduction
This document summarizes changes since BIND 9.10.6.
BIND 9.10.6-P1 addresses the security issue described in CVE-2017-3145.
Download
The latest versions of BIND 9 software can always be found at
http://www.isc.org/downloads/. There you will find additional
information about each release, source code, and pre-compiled versions
for Microsoft Windows operating systems.
New DNSSEC Root Key
ICANN is in the process of introducing a new Key Signing Key (KSK) for
the global root zone. BIND has multiple methods for managing DNSSEC
trust anchors, with somewhat different behaviors. If the root key is
configured using the managed-keys statement, or if the pre-configured
root key is enabled by using dnssec-validation auto, then BIND can keep
keys up to date automatically. Servers configured in this way should
have begun the process of rolling to the new key when it was published
in the root zone in July 2017. However, keys configured using the
trusted-keys statement are not automatically maintained. If your server
is performing DNSSEC validation and is configured using trusted-keys,
you are advised to change your configuration before the root zone
begins signing with the new KSK. This is currently scheduled for
October 11, 2017.
This release includes an updated version of the bind.keys file
containing the new root key. This file can also be downloaded from
https://www.isc.org/bind-keys .
Windows XP No Longer Supported
As of BIND 9.10.6, Windows XP is no longer a supported platform for
BIND, and Windows XP binaries are no longer available for download from
ISC.
Security Fixes
* Addresses could be referenced after being freed during resolver
processing, causing an assertion failure. The chances of this
happening were remote, but the introduction of a delay in
resolution increased them. (The delay will be addressed in an
upcoming maintenance release.) This bug is disclosed in
CVE-2017-3145. [RT #46839]
* An error in TSIG handling could permit unauthorized zone transfers
or zone updates. These flaws are disclosed in CVE-2017-3142 and
CVE-2017-3143. [RT #45383]
* The BIND installer on Windows used an unquoted service path, which
can enable privilege escalation. This flaw is disclosed in
CVE-2017-3141. [RT #45229]
* With certain RPZ configurations, a response with TTL 0 could cause
named to go into an infinite query loop. This flaw is disclosed in
CVE-2017-3140. [RT #45181]
Feature Changes
* dig +ednsopt now accepts the names for EDNS options in addition to
numeric values. For example, an EDNS Client-Subnet option could be
sent using dig +ednsopt=ecs:.... Thanks to John Worley of Secure64
for the contribution. [RT #44461]
* Threads in named are now set to human-readable names to assist
debugging on operating systems that support that. Threads will have
names such as "isc-timer", "isc-sockmgr", "isc-worker0001", and so
on. This will affect the reporting of subsidiary thread names in ps
and top, but not the main thread. [RT #43234]
* DiG now warns about .local queries which are reserved for Multicast
DNS. [RT #44783]
Bug Fixes
* Fixed a bug that was introduced in an earlier development release
which caused multi-packet AXFR and IXFR messages to fail validation
if not all packets contained TSIG records; this caused
interoperability problems with some other DNS implementations. [RT
#45509]
* Semicolons are no longer escaped when printing CAA and URI records.
This may break applications that depend on the presence of the
backslash before the semicolon. [RT #45216]
* AD could be set on truncated answer with no records present in the
answer and authority sections. [RT #45140]
End of Life
The end of life for BIND 9.10 is yet to be determined but will not be
before BIND 9.12.0 has been released for 6 months.
https://www.isc.org/downloads/software-support-policy/
Version 1.0.21
- Updating fast_tls to version 1.0.20.
- Updating stun to version 1.0.20.
Version 1.0.20
- Updating stun to version 1.0.19.
- Updating fast_tls to version 1.0.19.
Version 1.0.19
- Updating stun to version 1.0.18.
- Updating fast_tls to version 71250ae.
- Support SNI for TLS connections
Version 1.0.20
- Updating fast_tls to version 1.0.20.
Version 1.0.19
- Updating fast_tls to version 1.0.19.
Version 1.0.18
- Updating fast_tls to version 71250ae.
- Fix compilation warnings
Changes:
version 2018.01.14
Extractors
* [youtube] Fix live streams extraction (#15202)
* [wdr] Bypass geo restriction
* [wdr] Rework extractors (#14598)
+ [wdr] Add support for wdrmaus.de/elefantenseite (#14598)
+ [gamestar] Add support for gamepro.de (#3384)
* [viafree] Skip rtmp formats (#15232)
+ [pandoratv] Add support for mobile URLs (#12441)
+ [pandoratv] Add support for new URL format (#15131)
+ [ximalaya] Add support for ximalaya.com (#14687)
+ [digg] Add support for digg.com (#15214)
* [limelight] Tolerate empty pc formats (#15150, #15151, #15207)
* [ndr:embed:base] Make separate formats extraction non fatal (#15203)
+ [weibo] Add extractor (#15079)
+ [ok] Add support for live streams
* [canalplus] Fix extraction (#15072)
* [bilibili] Fix extraction (#15188)
version 2018.01.07
Core
* [utils] Fix youtube-dl under PyPy3 on Windows
* [YoutubeDL] Output python implementation in debug header
Extractors
+ [jwplatform] Add support for multiple embeds (#15192)
* [mitele] Fix extraction (#15186)
+ [motherless] Add support for groups (#15124)
* [lynda] Relax URL regular expression (#15185)
* [soundcloud] Fallback to avatar picture for thumbnail (#12878)
* [youku] Fix list extraction (#15135)
* [openload] Fix extraction (#15166)
* [lynda] Skip invalid subtitles (#15159)
* [twitch] Pass video id to url_result when extracting playlist (#15139)
* [rtve.es:alacarta] Fix extraction of some new URLs
* [acast] Fix extraction (#15147)
version 2017.12.31
Core
+ [extractor/common] Add container meta field for formats extracted
in _parse_mpd_formats (#13616)
+ [downloader/hls] Use HTTP headers for key request
* [common] Use AACL as the default fourcc when AudioTag is 255
* [extractor/common] Fix extraction of DASH formats with the same
representation id (#15111)
Extractors
+ [slutload] Add support for mobile URLs (#14806)
* [abc:iview] Bypass geo restriction
* [abc:iview] Fix extraction (#14711, #14782, #14838, #14917, #14963, #14985,
#15035, #15057, #15061, #15071, #15095, #15106)
* [openload] Fix extraction (#15118)
- [sandia] Remove extractor
- [collegerama] Remove extractor
+ [mediasite] Add support for sites based on Mediasite Video Platform (#5428,
#11185, #14343)
+ [ufctv] Add support for ufc.tv (#14520)
* [pluralsight] Fix missing first line of subtitles (#11118)
* [openload] Fallback on f-page extraction (#14665, #14879)
* [vimeo] Improve password protected videos extraction (#15114)
* [aws] Fix canonical/signed headers generation on python 2 (#15102)
Upstream changes:
mikutter 3.6.1
* happy new year
* honor iPhone X
* require Diva gem 0.3.1 or later
* JSON exported Time was not in iso8601 format
* Spell to update user profile (thanks shibafu528)
* fix typo (thanks akkiesoft)
* twitter: crash when using World other than Twitter due to wrong assumption
that User#idname was always defined
* openimg: sporadic crash when opening images
version 4.2.3 stable:
* API change: previously ZMQ_POLLOUT on a ZMQ_ROUTER socket returned always
true due to how the type works. When ZMQ_ROUTER_MANDATORY is set, sending
fails when the peer is not available, but ZMQ_POLLOUT always returns true
anyway, which does not make sense. Now when ZMQ_ROUTER_MANDATORY is set,
ZMQ_POLLOUT on a ZMQ_ROUTER will return true only if at least one peer is
available.
Given ZMQ_POLLOUT with ZMQ_ROUTER was not usable at all previously, we do
not consider this a breakage warranting a major or minor version increase.
* ZMQ_IDENTITY has been renamed to ZMQ_ROUTING_ID and ZMQ_CONNECT_RID has been
renamed to ZMQ_CONNTECT_ROUTING_ID to disambiguate. ZMQ_IDENTITY and
ZMQ_CONNECT_RID are still available to keep backward compatibility, and will
be removed in a future release after further advance notice.
* DRAFT API change: zmq_poller_wait, zmq_poller_wait_all and zmq_poller_poll
have been changed to be inline with other existing APIs that have a timeout
to return EAGAIN instead of ETIMEDOUT as the errno value.
* Existing non-DRAFT socket types ZMQ_REP/REQ, ZMQ_ROUTER/DEALER and
ZMQPUB/SUB, that were previously declared deprecated, have been reinstated
as stable and supported.
* Tweetnacl: add support for, and use preferably if available, getrandom() as
a simpler and less error-prone alternative to /dev/urandom on OSes where it
is available (eg: Linux 3.18 with glibc 2.25).
* Curve: all remaining traces of debug output to console are now removed, and
new DRAFT events are available to properly debug CURVE, PLAIN, GSSAPI and
ZAP events and failures. See below for details on the new events.
* New DRAFT (see NEWS for 4.2.0) socket options:
- ZMQ_GSSAPI_PRINCIPAL_NAMETYPE and ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE, for
the corresponding GSSAPI features. Additional definitions for principal
name types:
- ZMQ_GSSAPI_NT_HOSTBASED
- ZMQ_GSSAPI_NT_USER_NAME
- ZMQ_GSSAPI_NT_KRB5_PRINCIPAL
See doc/zmq_gssapi.txt for details.
- ZMQ_BINDTODEVICE (Linux only), which will bind the socket(s) to the
specified interface. Allows to use Linux VRF, see:
https://www.kernel.org/doc/Documentation/networking/vrf.txt
NOTE: requires the program to be ran as root OR with CAP_NET_RAW
- ZMQ_ZAP_ENFORCE_DOMAIN, enables strict RFC 27 compatibility mode and makes
the ZAP Domain mandatory when using security. See:
https://rfc.zeromq.org/spec:27/ZAP
See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.
* New DRAFT (see NEWS for 4.2.0) context options:
- ZMQ_THREAD_AFFINITY_CPU_ADD and ZMQ_THREAD_AFFINITY_CPU_REMOVE (Posix only),
to add and remove CPUs to the affinity set of the I/O threads. Useful to pin
the background threads to specific CPUs.
- ZMQ_THREAD_NAME_PREFIX (Posix only), to add a specific integer prefix to the
background threads names, to easily identify them for debugging purposes.
See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.
* New DRAFT (see NEWS for 4.2.0) message property name definitions to facilitate
the use of zmq_msg_gets:
- ZMQ_MSG_PROPERTY_ROUTING_ID
- ZMQ_MSG_PROPERTY_SOCKET_TYPE
- ZMQ_MSG_PROPERTY_USER_ID
- ZMQ_MSG_PROPERTY_PEER_ADDRESS
See doc/zmq_msg_gets.txt for details.
* New DRAFT (see NEWS for 4.2.0) API zmq_socket_get_peer_state, to be used to
query the state of a specific peer (via routing-id) of a ZMQ_ROUTER socket.
* New DRAFT (see NEWS for 4.2.0) Socket Monitor events:
- ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL, unknown system error and returns errno
- ZMQ_EVENT_HANDSHAKE_SUCCEEDED, handshake was successful
- ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL, protocol errors between peers or server
and ZAP handler. Returns one of ZMQ_PROTOCOL_ERROR_* - see manpage for list
- ZMQ_EVENT_HANDSHAKE_FAILED_AUTH, failed authentication, returns ZAP status
These events trigger when the ZMTP security mechanism handshake is
completed or failed. See doc/zmq_socket_monitor.txt for more information.
* New DRAFT (see NEWS for 4.2.0) zmq_proxy_steerable command 'STATISTICS' to
retrieve stats about the amount of messages and bytes sent and received by
the proxy. See doc/zmq_proxy_steerable.txt for more information.
* Add new autoconf --disable-libunwind option to stop building with libunwind
even if it is available.
* Add new autoconf --disable-Werror option to avoid building with the Werror
flag.
* Use pkg-config as the first method for finding and building with external
optional dependencies such as libnorm, libpgm and gssapi.
* On Posix platform where the feature is available, name the ZMQ background
threads to simplify debugging: "ZMQbg/<num_thread>"
* Improve performance of zmq_poller_* (and zmq_poll and zmq_proxy when building
with DRAFT APIs enabled).
* The TCP unit tests have been refactored to bind and connect to random ports
rather than hard-coded ones, to allow running tests in parallel.
There are 6 exceptions where it is necessary to use an hard-coded port to
test specific code paths that would not be exercised when binding to a
wildcard port. These are listed in tests/testutil.hpp so that distributions
can easily patch them if they wish to and so that they can be unique across
all the tests, allowing parallel runs.
The IPC unit tests have been changed as well to use unique socket file names
per test, where before there were some clashes.
* Fixed 2349 - fix building with libsodium when using CMake
* Fixed 2334 - do not assert when tuning socket options fails due to network
errors, but simply retry again when connecting or send a socket monitor
ZMQ_EVENT_ACCEPT_FAILED event when binding
* Fixed 2341 - fix source files path in VS2015 solution
* Fixed 2344 - Note that on Windows with VS2012 it is mandatory to increase
the default stack size to at least 2MB
* Fixed 2348 - ZMQ_ROUTER send with ZMQ_ROUTER_MANDATORY can be stuck in case of
network problem
* Fixed 2358 - occasional abort on zmq_connect on Windows
* Fixed 2370 - zmq_curve_keypair should return an error on failure rather
than ignoring them and always returning 0
* Fixed 2452 - __STDC_LIMIT_MACROS before precompiled headers causes VC++
warning
* Fixed 2457 - fix building with libsodium in Visual Studio solutions
* Fixed 2466 - add const qualifier to internal and public API that does not
modify parameters
* Fixed 2471 - do more checks for OOM conditions when dynamic allocations is
used
* Fixed 2476 - assertion causes abort after ZAP stop at shutdown
* Fixed 2479 - improve zmq_poller performance on Windows
* Fixed 2481 - potential memory leaks due to ZMTP handshake failures
* Fixed 2531 - ZMQ_GSSAPI_PRINCIPAL sockopt has no effect on client side
* Fixed 2535 - add BUILD_SHARED and BUILD_STATIC options to CMake, both on by
default, to toggle shared and static library builds
* Fixed 2537 - use SYSTEM_CLOCK on OSX and CLOCK_MONOTONIC elsewhere for
internal timers to avoid races
* Fixed 2540 - new zmq_poller used by zmq_poll without DRAFTs
* Fixed 2552 - Fix WITH_DOC CMake build to avoid checking for asciidoc if the
option is disabled
* Fixed 2567 - Memory leak in REP socket handling
* Fixed 2579 - Compilation issue on Windows with CMake + ninja
* Fixed 2588 - SIGBUS under 64-bit SunOS Sparc
* Fixed 2590 - crash when using ZMQ_IMMEDIATE and ZMQ_LINGER to non-zero
* Fixed 2601 - XPUB_MANUAL subscriptions not removed on peer term
* Fixed 2602 - intermittent memory leak for ZMQ_REQ/REP send/recv
* Fixed 2608 - CURVE server (connect) fails when client rebinds
* Fixed 2610 - print backtraces in mutual exclusion to avoid mixing
different traces
* Fixed 2621 - add missing CMake files to distributable tarball
* Fixed 2630 - improve compatibility with OpenBSD w.r.t. IPV6_V6ONLY
* Fixed 2638 - note in INSTALL that when using Windows builds on Linux with
Wine it is necessary to increase the minimum TCP buffers
* Fixed 2632 - Fix file descriptor leak when using Tweetnacl (internal NACL
implementation) instead of Libsodium, and fix race condition when using
multiple ZMQ contexts with Tweetnacl
* Fixed 2681 - Possible buffer overflow in CURVE mechanism handshake.
NOTE: this was protected by an assert previously, so there is no security
risk.
* Fixed 2704 - test_sockopt_hwm fails occasionally on Windows
* Fixed 2701 - pgm build via cmake doesn't link libzmq with libpgm
* Fixed 2711 - ZAP handler communication errors should be handled consistently
* Fixed 2723 - assertion in src\select.cpp:111 or hang on zmq_ctx_destroy on
Windows
* Fixed 2728 - fix support O_CLOEXEC when building with CMake
* Fixed 2761 - improve compatibility with TrueOS (FreeBSD 12)
* Fixed 2764 - do not unlink IPC socket files when closing a socket to avoid
race conditions
* Fixed 2770 - support lcov 1.13 and newer
* Fixed 2787 - add libiphlpapi to PKGCFG_LIBS_PRIVATE for static mingw builds
* Fixed 2788 - document that adding -DZMQ_STATIC is required for Windows
static builds with Mingw
* Fixed 2789 - description of zmq_atomic_counter_value return value is cloned
from zmq_atomic_counter_new
* Fixed 2791 - fix building with DRAFT APIs on CentOS 6
* Fixed 2794 - router_t methods should not allocate memory for lookup in
outpipes
* Fixed 2809 - optimize select() usage on Windows
* Fixed 2816 - add CMake and autoconf check for accept4, as it is not
available on old Linux releases, and fallback to accept + FD_CLOEXEC
* Fixed 2824 - ZMQ_REQ socket does not report ZMQ_POLLOUT when ZMQ_REQ_RELAXED
is set
* Fixed 2827 - add support for Haiku
* Fixed 2840 - fix building with VS2008
* Fixed 2845 - correct the ZMQ_LINGER documentation to accurately reflect that
the default value is -1 (infinite). It never was 30 second in any released
version, it was only changed briefly and then changed back, but the manpage
was not reverted.
* Fixed 2861 - CMake/MSVC: export ZMQ_STATIC when needed.
Changes:
1.1.2
-----
* Added support for:
* `puremashiro` (#66)
* `idolcomplex`
* Added an option to filter reblogs on `tumblr` (#61)
* Added OAuth user authentication for `tumblr` (#65)
* Added support for `slideshare` mobile URLs (#67)
* Improved pagination for various ...booru sites to work around page limits
* Fixed chapter information parsing for certain manga on `kissmanga` (#58) and `batoto` (#60)
Changelog:
## Bug Fixes
The following bugs have been fixed:
wnpa-sec-2018-01
Multiple dissectors could crash. (Bug 14253) CVE-2018-5336
wnpa-sec-2018-03
The IxVeriWave file parser could crash. (Bug 14297) CVE-2018-5334
wnpa-sec-2018-04
The WCP dissector could crash. (Bug 14251) CVE-2018-5335
Prior to this release dumpcap enabled the Linux kernel's BPF JIT compiler
via the net.core.bpf_jit_enable sysctl. This could make systems
more vulnerable to Spectre variant 1 (CVE-2017-5753) and this feature
has been removed (Bug 14313).
Some keyboard shortcut mix-up has been resolved by assigning
new shortcuts to Edit -> Copy methods.
Remote interfaces are not saved. (Bug 8557)
Additional grouping in Expert Information dialog. (Bug 11753)
First start with non-empty extcap folder after install or reboot
hangs at "initializing tap listeners". (Bug 12845)
Can't hide expert categories in Expert Information. (Bug 13831)
Expert info dialog should have "Collapse All"/"Expand All" options.
(Bug 13842)
SIP Statistics extract does not work. (Bug 13942)
Service Response Time - SCSI dialog crashes. (Bug 14144)
Wireshark & Tshark 2.4.2 core dumps with segmentation fault. (Bug 14194)
SSH remote capture promiscuous mode. (Bug 14237)
SOCKS pseudo header displays incorrect Version value. (Bug 14262)
Only first variable of list is dissected in NTP Control request
message. (Bug 14268)
NTP Authenticator field dissection fails if padding is used. (Bug 14269)
BSSAP packet dissector issue - BSSAP_UPLINK_TUNNEL_REQUEST message.
(Bug 14289)
"[Malformed Packet]" for Mobile IP (MIP) protocol. (Bug 14292)
There is a potential buffer underflow in File_read_line function in
epan/wslua/wslua_file.c file. (Bug 14295)
Saving a temporary capture file may not result in the temporary
file being removed. (Bug 14298)
## Updated Protocol Support
Bluetooth, BSSAP, BT ATT, BT HCI, BT SMP, MIP, NTP, SCTP, SOCKS, UDS, and WCP
Bugfixes:
#1845: Files on deduplicated NTFS volumes are ignored by scanner
#4590: Path completion in new folder dialog does not work anymore
#4593: Fd leak when temp file cannot be truncated
#4605: Panic: runtime error related to KCP
Enhancements:
#2644: UI for debug levels and log access
#4369: GUI should indicate which files are out of sync on remote devices
#4400: Keep enough counters and state in the database to avoid initial database traversal
#4515: Should understand “socks” in addition to “socks5” in proxy URLs
Other issues:
#4407: Contribute kcp-go changes/features and/or fix tests
#4585: Update vendored github.com/minio/sha256-simd for AVX512 support
#4615: Update vendored x/sys/unix for dragonfly
Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
The 0.3.2 series includes our long-anticipated new onion service
design, with numerous security features. (For more information, see
our blog post at https://blog.torproject.org/fall-harvest.) We also
have a new circuit scheduler algorithm for improved performance on
relays everywhere (see https://blog.torproject.org/kist-and-tell),
along with many smaller features and bugfixes.
gsutil is a Python application that lets you access Google Cloud Storage and
Amazon S3 from the command line. You can use gsutil to do a wide range of
bucket and object management tasks, including:
* Creating and deleting buckets
* Uploading, downloading, and deleting objects
* Listing buckets and objects
* Moving, copying, and renaming objects
* Editing object and bucket ACLs
