Changes since 4.13.10
* BUG 14769: smbd panic on force-close share during offload write.
* BUG 14731: Fix returned attributes on fake quota file handle and avoid
hitting the VFS.
* BUG 14783: smbd "deadtime" parameter doesn't work anymore.
* BUG 14787: net conf list crashes when run as normal user.
* BUG 14607: Work around special SMB2 READ response behavior of NetApp Ontap
7.3.7.
* BUG 14793: Start the SMB encryption as soon as possible.
* BUG 14792: Winbind should not start if the socket path for the privileged
pipe is too long.
Add option to disable afp session timeouts.
Fix setting of phase1 addresses on NetBSD.
Send replies to client when printing to prompt more data to be sent.
ok markd@.
Upstream changes:
0.98 2021-03-22
- document how to use buckets with dots, Signature V4, and HTTPS together
- fix Net::Amazon::S3::Client::Object::exists (#94)
- improve compatibility with DigitalOcean Spaces (#95)
0.97 2020-10-09
- presigned object access uri supports also PUT/DELETE methods (#89)
0.96 2020-10-07
- Signature V4 didn't work properly for services on non-standard port (issue #88)
0.95 2020-10-06
- bugfix release, with new test coverage
- small cleanups
0.94 2020-09-27
- fix undefined method call in still untested methods (thanks Russell Jenkins)
0.93 2020-09-27
- fix syntax failures on perl < v5.22 (thanks cpantesters)
0.92 2020-09-26
- misc cleanups, more tests
- Net::Amazon::S3::Client now can be constructed with same arguments as Net::Amazon::S3
- Support explicit ACL in bucket/object/upload creation
- Support set_acl on Client::Bucket / Client::Object (issue #83)
- Add support for bucket/object tagging (issue #44)
* Noteworthy changes in release 1.21.2 (2021-09-07)
** Support for autoconf 2.71
** Fix a double free in FTP when using an absolute path
** Release tarballs no longer have a dependency on Python.
** --page-requisites will now also download links marked as "alternate
stylesheet" or "icon"
Upstream changes:
2020-09-22 Todd Rinaldo <toddr@cpan.org> (0.49)
* Perl 5.6 is the minimum required version now.
* RIP Thread.pm it has not been relevant since 5.6
* Now using github CI to monitor the major platforms.
* .gitignore for better management
* Update the MANIFEST
* Perltidy the code base.
* use strict, warnings, no vars, our
* Remove perl 4-ish subroutine calls
* Require Sys::Syslog 0.29 to function properly.
* t/base.t -> Test::More
* Improve skipall messages and detection of ithreads/forks
* Disable t/ithreadm.t for Windows See https://github.com/toddr/Net-Daemon/issues/19
* Only load threads if forks hasn't already been loaded and threads exist.
* Update tracker location to github
* Fix ReadConfigFile implementation traversing @INC
Upstream changes:
**** 1.32 Jul 16, 2021
Text: Offer both Unicode and escaped-ASCII strings.
Add LICENSE file to comply with Fedora/RedHat announcement.
Fix rt.cpan.org #136666
Net::DNS::RR::ZoneFile parser erroneously strips line
terminators in quoted string forming part of multiline RR.
**** 1.31 May 2, 2021
Improve implementation of SVCB record.
Drop two patches applied upstream.
Take MAINTAINERship.
upstream NEWS:
perf 2.1.4 has many user visible changes since 2.0.13 and even more since
2.0.5 The below describes many of these user visible changes with
a focus on 2.1.4 compared to 2.0.13
-e or --enhanced-reports
configure '--enable-fast-sampling'
This configuration causes the iperf binary to support units
of microseconds. It casues iperf to use four units of precision
in it's timing interval output, i.e. 1e-4, as one example
iperf -c 192.168.1.64 -n 4 -C
------------------------------------------------------------
Client connecting to 192.168.1.64, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.1.133 port 56568 connected with 192.168.1.64 port 5001
[ ID] Interval Transfer Bandwidth
[ 1] 0.0000-0.0172 sec 4.00 Bytes 1.86 Kbits/sec
'--trip-times' on the client
This option indicates to iperf a few things. First, that the user
has syncrhonized the clients' and servers' clocks. A good way to do
this is using Precision Time Protocol and a GPS atomic clock as a
reference. This knowledge allows iperf to use many time stamps
to be sender based, i.e. taken from the sender's write timestamp
(which is carried in the payloads.)
The connect message on both the server and the client will indicate
that '--trip-times' has been enabled.
Both UDP an TCP support '--trip-times'
iperf -c 192.168.1.64 --trip-times
------------------------------------------------------------
Client connecting to 192.168.1.64, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.1.133 port 56580 connected with 192.168.1.64 port 5001 (trip-times)
iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 128 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.1.64%enp2s0 port 5001 connected with 192.168.1.133 port 56580 (MSS=1448) (trip-times) (sock=4) (peer 2.1.4) on 2021-08-22 11:12:08 (PDT)
Iperf 2 new metrics
NetPwr
Network power: The network power (NetPwr) metric originates from Kleinrock and Jaffe circa 1980.
It is a measure of a desirable property divided by an undesirable property.
It is defined as throughput/delay. For TCP transmits, the delay is the sampled RTT times.
For TCP receives, the delay is the write to read latency. For UDP the delay is the
packet end/end latency.
Note, one must use -i interval with TCP to get this as that's what sets the RTT sampling rate.
The metric is scaled to assist with human readability.
InP
The InP metric is derived from Little's Law or Little's Lamma. LL in queuing theory is a
theorem that determines the average number of items (L) in a stationary queuing system
based on the average waiting time (W) of an item within a system and the average number
of items arriving at the system per unit of time (lambda). Mathematically,
it's L = lambda * W. As used here, the units are bytes. The arrival rate is
taken from the writes.
The ChangeLog doesn't explicitly mention, but this fixes the CVE-2021-40346
vulnerability as described in:
https://www.mail-archive.com/haproxy@formilux.org/msg41114.html
While here switch to inserting CFLAGS via CPU_CFLAGS, as that feels a little
more appropriate than DEBUG_CFLAGS after re-reading the Makefile.
2021/09/07 : 2.4.4
- BUG/MEDIUM: h2: match absolute-path not path-absolute for :path
- REGTESTS: http_upgrade: fix incorrect expectation on TCP->H1->H2
- REGTESTS: abortonclose: after retries, 503 is expected, not close
- MINOR: hlua: take the global Lua lock inside a global function
- BUG/MINOR: stick-table: fix the sc-set-gpt* parser when using expressions
- BUG/MEDIUM: base64: check output boundaries within base64{dec,urldec}
- BUG/MINOR: base64: base64urldec() ignores padding in output size check
- MINOR: compiler: implement an ONLY_ONCE() macro
- BUG/MINOR: lua: use strlcpy2() not strncpy() to copy sample keywords
- BUG/MINOR: time: fix idle time computation for long sleeps
- MINOR: time: add report_idle() to report process-wide idle time
- BUG/MINOR: ebtree: remove dependency on incorrect macro for bits per long
- BUG/MINOR threads: Use get_(local|gm)time instead of (local|gm)time
- BUG/MINOR: tools: Fix loop condition in dump_text()
- CLEANUP: Add missing include guard to signal.h
- BUG/MINOR: vars: fix set-var/unset-var exclusivity in the keyword parser
- DOC: configuration: remove wrong tcp-request examples in tcp-response
- BUG/MINOR: config: reject configs using HTTP with bufsize >= 256 MB
- CLEANUP: htx: remove comments about "must be < 256 MB"
- BUG/MAJOR: htx: fix missing header name length check in htx_add_header/trailer
- Revert "BUG/MINOR: stream-int: Don't block reads in si_update_rx() if chn may receive"
There is something wrong in tor's makefiles which causes:
src/lib/version/git_revision.c:21:10: fatal error: micro-revision.i: No such file or directory
#include "micro-revision.i"
^~~~~~~~~~~~~~~~~~
compilation terminated.
obviously by not having built micro-revision.i when that compilation
is done. This happens reliably for some people and not for others.
This commit adds a comment with the issue in tor's bug tracker, and a
workaround that builds micro-revision.i and then does the normal
build.
No PKGREVISION as this is just a build fix, and should have zero
effect if this built anyway.
ok @wiz
upstream changes are bugfixes and minor improvements plus:
Improvements
Allow dismissing UDM-Pro banner in dashboard page.
Add "Firmware version" column to Devices page and change "Version" to "Firmware Status".
Add alert that threat was detected or blocked.
Add 'Sign Out' button for Software installation controller.
Add USW-Enterprise-24-PoE images.
Add USP-RPS panel overview and port diagram.
Add status indicators to Clients table.
Add date range to Statistics.
Add L3 Switch routing support for Static Route.
Live update performance improvements in all pages.
Improve Statistics page performance.
Improve Hotspot form performance.
Improve alert client fingerprinting.
Remove frequent alerts after 14 days.
Update WiFiman Topology in property panel.
Update admin role names (Administrator, Site Admin, View only, Hotspot Operator).
Update VPN section.
Column visibility for Device and Client tables.
Save table columns only when leaving page.
Updates to side navigation icons.
Utilization-bar tooltip style updates.
Capitalize MAC and WLAN text used in property panel.
Always send connection alert for clients.
Move table row actions to forms.
Update UAP property panel.
Remove survey modals from Dashboard and Settings.
Traffic section design updates.
Implement Device and Outlets sections for USP-RPS property panel.
0.36.2
Include NSEC records for non-existent types when responding with addresses
0.36.1
Skip goodbye packets for addresses when there is another service registered with the same name
If a ServiceInfo that used the same server name as another ServiceInfo was unregistered, goodbye packets would be sent for the addresses and would cause the other service to be seen as offline.
Fixed equality and hash for dns records with the unique bit
These records should have the same hash and equality since the unique bit (cache flush bit) is not considered when adding or removing the records from the cache.
0.36.0
Technically backwards incompatible:
Fill incomplete IPv6 tuples to avoid WinError on windows
0.35.1
Only reschedule types if the send next time changes
When the PTR response was seen again, the timer was being canceled and rescheduled even if the timer was for the same time. While this did not cause any breakage, it is quite inefficient.
Cache DNS record and question hashes
The hash was being recalculated every time the object was being used in a set or dict. Since the hashes are effectively immutable, we only calculate them once now.
0.35.0
Reduced chance of accidental synchronization of ServiceInfo requests
Sort aggregated responses to increase chance of name compression
Technically backwards incompatible:
Send unicast replies on the same socket the query was received
When replying to a QU question, we do not know if the sending host is reachable from all of the sending sockets. We now avoid this problem by replying via the receiving socket. This was the existing behavior when InterfaceChoice.Default is set.
This change extends the unicast relay behavior to used with InterfaceChoice.Default to apply when InterfaceChoice.All or interfaces are explicitly passed when instantiating a Zeroconf instance.
0.34.3
Fix sending immediate multicast responses
0.34.2
Coalesce aggregated multicast answers
When the random delay is shorter than the last scheduled response, answers are now added to the same outgoing time group.
This reduces traffic when we already know we will be sending a group of answers inside the random delay window described in datatracker.ietf.org/doc/html/rfc6762#section-6.3
Ensure ServiceInfo requests can be answered inside the default timeout with network protection
Adjust the time windows to ensure responses that have triggered the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 can respond in under 1350ms to ensure ServiceInfo can ask two questions within the default timeout of 3000ms
0.34.1
Ensure multicast aggregation sends responses within 620ms
Responses that trigger the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 could cause the multicast aggregation response to be delayed longer than 620ms (The maximum random delay of 120ms and 500ms additional for aggregation).
Only responses that trigger the protection are delayed longer than 620ms
0.34.0
Implemented Multicast Response Aggregation
Responses are now aggregated when possible per rules in RFC6762 section 6.4
Responses that trigger the protection against against excessive packet flooding due to software bugs or malicious attack described in RFC6762 section 6 are delayed instead of discarding as it was causing responders that implement Passive Observation Of Failures (POOF) to evict the records.
Probe responses are now always sent immediately as there were cases where they would fail to be answered in time to defend a name.
0.33.4
Ensure zeroconf can be loaded when the system disables IPv6
Upstream changes:
2.010 Mar 22 2021
- Add SSL_verify_callback
- Fix SSLEAY connect spinloop
- Various pod typos
- Allow for logging to STDOUT for HTTP
- Add PATCH verb to HTTP
Upstream changes:
1.93 Jan 19, 2021
- put_content was not handling optional arguments correctly
(bug report by Bas van Sisseren).
1.92_03 Oct 1, 2020
- Write buffer could grow uncontrolled after a connection
lost error (bug report by Jozef Kutej, #gh17).
1.92_02 Jun 25, 2020
- Fix handling of out of order responses.
1.92_01 Jun 24, 2020
- Add support for receiving out of order responses from the
server (bug report by Dimitar Kolev #rt130641 and ftumsh
#rt132768).
Upstream changes:
* Version 3.05 released.
2021-06-20 Jay Rogers <jay@rgrs.com>
* Telnet.pm: Fixed new perl warning about argument isn't numeric in
numeric ge (>=).
2021-05-30 Jay Rogers <jay@rgrs.com>
* Telnet.pm (dump_log input_log option_log output_log): Changed
the logging subroutines to also accept a tied filehandle.
2021-03-30 Jay Rogers <jay@rgrs.com>
* Telnet.pm (waitfor): Improved the speed to search for the
"match", especially when reading a large amount of data, by using
the dynamic arrays @- and @+ instead of $` and $&.
2021-03-30 Jay Rogers <jay@rgrs.com>
* Telnet.pm (new): Fixed a bug that caused the instantiation to
fail when setting one of the *_log input args to an empty string.
2020-02-20 Jay Rogers <jay@rgrs.com>
* Telnet.pm: Added a workaround for the "require FileHandle" bug in
perl 5.10.1.
2020-02-20 Jay Rogers <jay@rgrs.com>
* Telnet.pm: Stopped using the deprecated variable $[ in the
autoflush idiom select((select($fh), $|=1)[$[]).
2018-07-12 Jay Rogers <jay@rgrs.com>
* Telnet.pm: Fixed some documentation and pod command typos.
2013-04-21 Jay Rogers <jay@rgrs.com>
Upstream changes:
0.82 Wednesday January 6, 2021, 09:59:00 AM -0800
* Makefile.PL
* lib/RPC/XML/Server.pm
Bump version numbers.
* Makefile.PL
* lib/RPC/XML/Server.pm
* t/40_server.t
* t/40_server_xmllibxml.t
* t/41_server_hang.t
* t/60_net_server.t
* t/util.pl
RT #120472: Applied patch from Petr Písař for fixes to IPv6
support. Full detail in the message for this commit in the git
repository.
0.81 Tuesday January 5, 2021, 06:33:00 PM -0800
* MANIFEST
* perlcritic.rc (added)
Add a perlcritic.rc file for testers who run author tests.
* t/40_server.t
* t/40_server_xmllibxml.t
Remove redundant testing and general clean-up. Removed tests of
url() that were just re-testing HTTP::Daemon::url().
* lib/RPC/XML/Client.pm
Parameterize the request-as-string debug feature.
* lib/RPC/XML/Client.pm
Merge pull request #13 from
enrico-sorcinelli/add-request-string. Added xmlrpc request
string as object property. (Enrico Sorcinelli)
For some reason, Go 1.17 uses -mod=vendor as the default in this build and
complains about needing to update go.mod. Add a "-mod=readonly" to get it
to build.
I believe this is a relatively minor update, plus bringing python 3.x
support. Upstream does not publish NEWS or a changelog, and the
homepage does not even mention the release.
Update prompted by tahoe-lfas needing this (py3-compattible) version.
I am not aware of anything else needing it. If so and this version
isn't ok, we'll have to go to versioned_dependencies and import the
old one -- but this builds ok with 2.7.
3.7.4 (2021-06-22)
Merged Pull Requests
* Update chefstyle requirement from 1.7.5 to 2.0.3 #683 (dependabot[bot])
* Retry the Windows local pipe server connection once on EPIPE #694
(clintoncwolfe)
3.8.1 (2021-07-27)
Merged Pull Requests
* Update chefstyle requirement from 2.0.3 to 2.0.5 #695 (dependabot[bot])
* Remove pins for Ruby < 2.5 #688 (tas50)
* Parse Message : Added new message for lack of sudo privilege and appl…
#690 (msys-sgarg)
* Update chefstyle requirement from 2.0.5 to 2.0.7 #700 (dependabot[bot])
1.61.6 (2021-06-20)
* RD bit not set on Recursor queries (thanks Sean Dilda!)
* Handle quoted strings followed by unquoted strings in TXT records
* do not worry about rogue repeated Ids - just log an error and get on with
life
* Clear Ruby warnings
* Use GitHub Actions rather than Travis
1.61.7 (2021-06-23)
* Fix namespace issue from 1.61.6
2.8.0 (2021-07-03)
* fixes ReDoS vulnerability in Addressable::Template#match
* no longer replaces + with spaces in queries for non-http(s) schemes
* fixed encoding ipv6 literals
* the :compacted flag for normalized_query now dedupes parameters
* fix broken escape_component alias
* dropping support for Ruby 2.0 and 2.1
* adding Ruby 3.0 compatibility for development tasks
* drop support for rack-mount and remove Addressable::Template#generate
* performance improvements
* switch CI/CD to GitHub Actions
The software depends on compiler flags (-fwrapv) for specific overflow
handling, but for some strange reason instead of appending them during
the build regardless of what the user has set CFLAGS to, it allows
CFLAGS to be overridden and aborts at runtime! Passing in our CFLAGS
via DEBUG_CFLAGS, while not ideal, allows them to be properly combined.
Fix from goekesmi in joyent/pkgsrc#313. Bump PKGREVISION.
This takes advantage of the introduction of the SYSCONFBASE variable.
Tested on NetBSD/amd64.
While there, improve the general behaviour, and avoid `pkill -u` in particular
when stopping the service.
Bumps PKGREVISION.
3.55.1 (2012-08-09)
- Fixed a crash if a tree view items are deleted at the same time as something is being dragged over the tree view
- Updated to libfilezilla 0.31.1 to fix an issue with SIGPIPE on *nix
0.31.1 (2021-08-09)
+ Added iterator for JSON arrays
- *nix: SIGPIPE is now set to SIG_IGN the first time a pipe or socket gets created
- Handle empty search string in replace_subscripts
