IRRd v4.0.4.post1

This version fixes an issue in the release notes of 4.0.4. Otherwise, it is identical.

IRRd 4.0.4

IRRd 4.0.4 was released on July 15th, 2019, and contains
one change relating to the behaviour of changed:
attributes in RPSL objects.

In earlier versions of IRRd, format of the changed
attribute was entirely free. In IRRd 4.0.4, the format
is expected to be <email> [YYYYMMDD] with an optional
comment, as allowed with other RPSL attributes. The date
is optional. Regardless of the date, if any, set in the
attribute, it will be overwritten by today’s date[1],
unless the override password was used. Pre-existing
changed attributes are not affected.

[1] #242

IRRd 4.0.3

IRRd 4.0.3 was released on June 29th, 2019, and contains
one change relating to referential integrity validation
between RPSL objects.

In earlier versions of IRRd, the members attribute of
an as-set, along with several others,
were strongly validated[1]. This meant it was not possible
to add or update an as-set, if some of the members were
not valid objects in the same source. The same applied
to fields like member-of in a route-set.

In IRRd 4.0.3, all references from members, mp-member,
mbrs-by-ref and member-of are weak references. Their
syntax is validated, e.g. for as-set members, values must
be a valid as-set name or a valid AS number. However, there
is no validation on whether the objects actually exist.
It is also possible to delete e.g. a route-set, even when
the object is still listed in the member-of in a route
object, or to reference a maintainer that does not exist
in a mbrs-by-ref.

[1] #240

IRRd 4.0.2

IRRd 4.0.2 includes one bugfix and two enhancements:

• A bug in IPv4 addresses in access lists[1] IPv6-mapped
  IPv4 addresses would be rejected, even when they were
  listed in the access list.
• Ignoring of *xx object classes[2], even in strict mode,
  as these are harmless artifacts sometimes produced by
  legacy IRRd versions.
• Adding an irrd_mirror_force_reload[3] command, to force
  a reload of a particular mirror. The irrd_load_data
  command was not well suited for this, and the documentation
  provides guidance on when to use which command.

IRRd 4.0.2 is entirely backwards compatible with 4.0.0.

[1] #237
[2] #232
[3] #233

IRRd 4.0.1

IRRd 4.0.1 fixes a bug in object deletion[1] and upgrades
the twisted version to 19.2.1 to ensure CVE-2019-12387 is
fixed.

The bug in object deletion prevented the deletion of
objects with no inbound references, such as certain route
objects. CVE-2019-12387 likely did not affect IRRd, as it
affected components of twisted that are not directly used
in IRRd, but upgrading is recommended to be sure.

IRRd 4.0.1 is entirely backwards compatible with 4.0.0.

[1] #228

IRRd 4.0.0

v4.0.0

Release 4.0.0

IRRd 4.0.0 release candidate 9

• Fix #212 - Restrict mntner creation to override password (#219)
• Disable nagle on whois sockets (#218)
• Fix #217 - Replace orderedset with more recent ordered-set dependency.
• Updated dependencies

IRRd 4.0.0 release candidate 8

NOTE: this release introduces a backwards incompatibility. The preloading feature adds a requirement for an --irrd_pidfile argument to the irrd_load_database and irrd_submit_email commands.

• Fix #184 - Add preloading for routes per origin.
• Fix #192 - Resolve as(-sets) contained in route-sets
• Fix #196 - Correct query source search order.
• Fix #172 - Add irrd_load_database command for manual loading of sources
• Fix #200 - Clarify error messages for queries with missing parameter
• Updated dependencies.

IRRd 4.0.0 release candidate 7

94a2420 Fix #168 - Add !t command to set timeout. (#193)
af2ad1d Fix #177 - Remove tracebacks from logs for mirror IO errors.
0a2c298 Fix #173 - Add logrotate and systemd config examples to docs.
d433c73 Fix #188 - Fix skipping over NRTM updates when reloading databases.
1f2f677 Fix incorrect setting name in configuration sample.
cc0b8ea Fix #186 - Do not delete existing data for non-NRTM when serial is too recent
7f76d5d Ref #177 - Moved some logs from CRITICAL to ERROR level.
135a39b Fix #180 - Issues with non-NRTM sources which do have serial files.
5940474 Fix #178 - Use sources_default order for !j-*
df93b18 Fix #181 - Use serial_seen rather than serial_journal in !j output

IRRd 4.0.0 release candidate 6

e8422e3 Fix #167 - Add bytes sent to post-query log message.
a9142da Set timeout to 600 seconds.
1d41f5c Add !a query for improved performance. Also switch to ujson for JSON decoding.

As a side effect of the !a work, some !i queries may be faster, as well as some queries with very large responses. Little effect should be expected on an aclgen that does not use !a though.