Skip to content

@mxsasha mxsasha released this Nov 12, 2019 · 42 commits to master since this release

IRRd 4.0.8 was released on November 12th, 2019.
It adds two minor features[1]:

  • An # EOF marker is added to the end of all exports.
  • Ordering in exports is now consistent between exports.

[1] #268

Assets 4

@mxsasha mxsasha released this Oct 3, 2019 · 42 commits to master since this release

IRRd 4.0.7 was released on October 3rd, 2019.
It fixes an issue where export permissions were not set correctly[1].
In 4.0.7, the files saved to sources.{name}.export_destination
always have their permissions set to 644.

[1] #258

Assets 4

@mxsasha mxsasha released this Sep 5, 2019 · 42 commits to master since this release

IRRd 4.0.6 was released on September 5th, 2019.

In 4.0.5, a performance issue was introduced while fixing
an issue where some queries
did not correctly filter for the selected sources[1].
The performance issue is resolved in 4.0.6.

[1] #251

Assets 4
Sep 2, 2019
IRRd release 4.0.5

@mxsasha mxsasha released this Sep 2, 2019 · 42 commits to master since this release

IRRd 4.0.5 was released on September 2nd, 2019, and fixes
two bugs.

4.0.5.post1 was released due to an incorrect version
number change in 4.0.5, which could cause confusion
on which version was running.

In earlier versions of IRRd, queries that looked up
the routes originating from a certain AS,
did not correctly filter for the selected sources[1].
Also, the !s-lc query did not always correctly display
which sources were currently selected.

[1] #251

Assets 4

@mxsasha mxsasha released this Jul 15, 2019 · 42 commits to master since this release

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

Assets 4

@mxsasha mxsasha released this Jul 15, 2019 · 42 commits to master since this release

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

Assets 4

@mxsasha mxsasha released this Jun 29, 2019 · 42 commits to master since this release

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

Assets 4

@mxsasha mxsasha released this Jun 26, 2019 · 42 commits to master since this release

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

Assets 4

@mxsasha mxsasha released this Jun 11, 2019 · 29 commits to stable/4.0.x since this release

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

Assets 4
You can’t perform that action at this time.