* Repeated warnings due to 'Recache Event Detected for Device'
* No error is recorded to log file when database is incorrect
* MySQL retry logic is not working as expected
* When using IPv6 address, segmentation fault can occur due to incorrectly
using IPv4 ping
* When polling results are null, segmentation errors may occur
* When collecting data, spine should be stripping alpha characters from output
This release introduces two handy features, please take a look
on http://mailman.nginx.org/pipermail/unit/2020-April/000199.html
for details.
<ChangeLog>
*) Feature: a "return" action with optional "location" for immediate
responses and external redirection.
*) Feature: fractional weights support for upstream servers.
*) Bugfix: accidental 502 "Bad Gateway" errors might have occurred in
applications under high load.
*) Bugfix: memory leak in the router; the bug had appeared in 1.13.0.
*) Bugfix: segmentation fault might have occurred in the router process
when reaching open connections limit.
*) Bugfix: "close() failed (9: Bad file descriptor)" alerts might have
appeared in the log while processing large request bodies; the bug
had appeared in 1.16.0.
*) Bugfix: existing application processes didn't reopen the log file.
*) Bugfix: incompatibility with some Node.js applications.
*) Bugfix: broken build on DragonFly BSD; the bug had appeared in
1.16.0.
</ChangeLog>
* Upstream's repository seems stale and no longer maintained. There was no
official release at PyPI since 2015 and the code isn't compatible with
Django 2.2 or later.
Thus deprecate the port and set an expiration date.
PR: 245644
Approved by: Kevin Golding <ports@caomhin.org> (maintainer)
* Repo-copy from www/py-django-happenings because it's an official fork and
also available at PyPI. The forked version has support for newer Django
releases.
* Update CONFLICTS_INSTALL entries accordingly but omit www/py-django-mptt
as it can co-exist (once assigned to Django 2.2) with
www/py-django-happenings-update.
PR: 245644
Approved by: Kevin Golding <ports@caomhin.org> (maintainer)
Some server administrators complained about us breaking the admin
port protocol. Sorry about that, we're bringing the old protocol
back now, your old tools will now work again.
Someone also found two crash bugs to fix, game script goal question
id's being truncated, and a display issue when refitting incredibly
large trains.
Found out via: repology.org
* Assign the port to Django 2.2 (current LTS release) because Django 1.11 is
End-of-Life since April.
* Switch back from Github to CHEESESHOP as sdist tarballs at PyPI are
available again.
* Also remove textproc/pootle from CONFLICTS_INSTALL as it no longer exists
in the Ports tree.
PR: 245643
Approved by: Kevin Golding <ports@caomhin.org> (maintainer)
ChangeLog:
https://github.com/ruben2020/codequery/blob/master/NEWS.md#version-0230---apr-15-2020
Accumulated changes:
* The CMake build directory is now moveable and renameable
* Enhancement: Added build option for no GUI
* Enhancement: Updated Scintilla to 3.11.2
* Enhancement: Performance improvement by using QString instead of STL String
for search through GUI
* Enhancement: Added ability to general call function and class inheritance
graph through cqsearch CLI
* Enhancement: Added ability to filter by path added to cqsearch CLI
* Enhancement: Changing query type on the GUI dropbox will start a search
immediately
* Enhancement: Clicking on a line in the GUI file viewer, will now highlight
the appropriate function in the function list
* Enhancement: Now Qt5 becomes the default build option in CMakeLists.txt
* Enhancement: Windows installer changed from InnoSetup to Wix Toolset, to
generate MSI installer
* Enhancement: Now Windows installer will be in two versions: Qt5, 64-bit or
Qt4, 32-bit
* Bugfix: Default font selection for GUI file viewer, instead of becoming
empty
* Bugfix: Improved annotation accuracy in GUI
* Bugfix: Improved brace highlighting in GUI
* Bugfix: Fixed the bug where function list next to GUI file viewer doesn't
work properly for grep
Reported by: portscout
There is a time frame between allocating peer-id and initializing data
channel key (which is performed on receiving push request or on async
push-reply) in which the existing peer-id float checks do not work right.
If a "rogue" data channel packet arrives during that time frame from another
address and with same peer-id, this would cause client to float to that new
address.
The net effect of this behaviour is that the VPN session for the "victim
client" is broken. Since the "attacker client" does not have suitable keys,
it can not inject or steal VPN traffic from the other session. The time
window is small and it can not be used to attack a specific client's session,
unless some other way is found to make it disconnect and reconnect first.
This fix is inherited by the openvpn-mbedtls slave port.
Obtained from: Lev Stipakov (OpenVPN)
MFH: 2020Q2 (blanket security patch)
Security: CVE-2020-11810
Security: 8604121c-7fc2-11ea-bcac-7781e90b0c8f
