Irrd

Latest version: v4.4.4

Safety actively analyzes 701507 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 12

4.0.7

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] https://github.com/irrdnet/irrd4/issues/258

4.0.6

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] https://github.com/irrdnet/irrd4/issues/251

4.0.5.post1

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] https://github.com/irrdnet/irrd4/issues/251

4.0.5

two bugs.

4.0.4.post1

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

4.0.4

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] https://github.com/irrdnet/irrd4/issues/242

Page 9 of 12

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.