Irrd

Second beta release of 4.3.0. Release notes: https://irrd.readthedocs.io/en/latest/releases/4.3.0/

First beta release of 4.3.0. Release notes: https://irrd.readthedocs.io/en/latest/releases/4.3.0/

* Set members included through mbrs-by-ref / member-of did not have the correct source filter applied. This meant that members could be included in a set, even through the aut-num, route or route6 object were from a different IRR source.
* The PyYAML dependency was updated to 6.0.1 to resolve installation issues in certain environments.

IRRd 4.2.8 was released on April 19th, 2023, and fixes an issue where NRTM queries could hang indefinitely on PyPy deployments (774). This did not affect CPython deployments.

* IRRd now has a new setting ``sources.{name}.nrtm_query_serial_range_limit``
to limit the maximum serial range a client may request in a single NRTM
query. This is configured per source, and evaluated in addition to
other access limits. By default, there is no limit.
See the :doc:`configuration documentation </admins/configuration>`
for details.
* Each IRRd process will now log a traceback of all threads when receiving
a SIGUSR1 signal. The tracebacks are written to the normal logs, and
can help IRRd developers understand more complex issues, particularly
in hanging IRRd workers.
* Password hashes were visible in some email notifications (722). The scope
was limited. A notification could only be triggered by already
knowing a valid password.

* IRRD whois connections could stay stuck in FIN_WAIT2 state (607), which may also have led to workers to stop responding (693) to queries in some cases. This was addressed by adding a missing timeout to read calls on these connections.
* A few small changes were made to improve unclear log messages.