Skip to content

Releases: NLnetLabs/routinator

0.13.1-rc1

13 Jul 14:42
01ec225
Compare
Choose a tag to compare
0.13.1-rc1 Pre-release
Pre-release

New

  • Added support for ASPA. Processing needs to be enabled via the new option enable-aspa which is only available if the aspa feature is explicitly selected during compilation. This is due to the specification still changing. The implementation currently conforms with draft-ietf-sidrops-aspa-profile-15. (#847, #873, #874, #878)
  • Added support for version 2 of the RTR protocol. This primarly means support for the ASPA payload type. (#847)
  • Sending SIGUSR2 to Routinator will re-open a log file if logging to a file is enabled. (#859)
  • The HTTP server provides a new endpoint /json-delta/notify that can be used to wait for updated data similar to the RTR Notify PDU. (#863)
  • Added support for filtering and adding router keys via local exception files. (#865)
  • The vrps command and the HTTP payload output endpoints now allow excluding specific payload types for output. (#866)
  • Added a new member payload to the output of the /api/v1/status endpoint that gives an overall summary of the produced payload. (#867)
  • Added new members generated and generatedTime to the JSON object produced by the /json-delta endpoint. (#868)

Breaking Changes

  • A new field aspa was added to the jsonext format. See the manual page for more information. (#847)
  • A number of ASPA-related fields have been added to all metrics and status formats. (#847)
  • Renamed functions and attributes that refer to standalone end entity certificates to refer to router certificates so they don’t get confused with the end entity certificates included with signed objects. (#854)
  • Renamed the JSON member in the HTTP status API from validEECerts to validRouterCerts. The old name is still available but may be removed in the future. (#854)
  • The regular json output format now includes router key and ASPA output. Since both are disabled by default, the format will still be compatible by default. (#866)
  • The minimal required Rust version has been increased to 1.70. (#847, #853, #869, #879)

Bug Fixes

  • Fixed a bug in the RTR server where it would include router key PDUs even if the negotiated protocol version was 0. (via rpki-rs #250)
  • Restored the ability to parse ASNs in JSON input to the validity command as string or number. (#861)

Other Changes

  • The log message for missing manifest now include the URI of the CA certificate for which the manifest is missing. (#864)
  • Binary packages are now also built for Debian bookworm. (#881)

0.12.1 ‘Plan uw reis in de app’

04 Jan 11:14
3f64770
Compare
Choose a tag to compare

Bug Fixes

  • Actually use the extra-tals-dir config file option. (#821)
  • Allow private keys prefixed both with BEGIN PRIVATE KEY and BEGIN RSA PRIVATE KEY in the files referred to by http-tls-key and rtr-tls-key configuration options. (#831, #832)
  • On Unix, if chroot is requested but no working directory is explicitly provided, set the working directory to the chroot directory. (#823)
  • Fixed the error messages printed when the http-tls-key or http-tls-cert options are required but missing. They now refer to HTTP and not, as previously, to RTR. (#824 by @SanderDelden)

Other Changes

0.12.1-rc2

13 Dec 13:08
cc37f14
Compare
Choose a tag to compare
0.12.1-rc2 Pre-release
Pre-release

Bug Fixes

  • Allow private keys prefixed both with BEGIN PRIVATE KEY and BEGIN RSA PRIVATE KEY in the files referred to by http-tls-key and rtr-tls-key configuration options. (#831, #832)

0.12.1-rc1

05 Dec 14:58
6eadecf
Compare
Choose a tag to compare
0.12.1-rc1 Pre-release
Pre-release

Bug Fixes

  • Actually use the extra-tals-dir config file option. (#821)
  • On Unix, if chroot is requested but no working directory is explicitly provided, set the working directory to the chroot directory. (#823)
  • Fixed the error messages printed when the http-tls-key or http-tls-cert options are required but missing. They now refer to HTTP and not, as previously, to RTR. (#824 by @SanderDelden)

Other Changes

0.12.0 ‘Brutalism and Gardening’

10 Nov 12:12
955795f
Compare
Choose a tag to compare

Breaking Changes

  • Restructured the TAL configuration in response to the dropped requirement to opt into the ARIN TAL.

    Routinator will now use the bundled RIR TALs directly unless told otherwise by the new --no-rir-tals command line and config option. The additional bundled TALs can be added via the new --tal command line and config option. Additionally, the TAL directory can still be used via the --extra-tals-dir option. The tal-dir option has been removed but will still be accepted – and ignored – in the config file only.

    The init command has been removed. (#796)

  • Changed the default configuration option for unsafe-vrps to accept and removed all logging or mentioning of unsafe VRPs in this case. (#761)

  • Setting the rsync-timeout option to 0 now disables the rsync timeout. (#798)

  • Refactored error handling. Routinator now logs the reason why an object failed verification or was otherwise rejected. (#755)

  • Removed the deprecated rrdp-disable-gzip configuration option. (#769)

New

  • The new limit-v4-len and limit-v6-len command line and config file options allow limiting the length of IPv4 and IPv6 prefixes, respectively, to be included in the VRP data set. (#810)
  • The new rrdp-fallback command line and config file option allows specifying the circumstances under which a failed RRDP fetch should result in using rsync instead. Supported polices are never for never falling back to using rsync, stale for the current behavior of falling back when RRDP has failed for some time, and new to only fall back for repositories where RRDP has never worked before. (#799)
  • In the extended jsonext output format, the information for VRPs and router keys derived from RPKI data has gained a new member "tal" that shows the name of the TAL this object was published under. (#765)
  • The log output to files, stderr, and the /log HTTP endpoint now includes the log level of the message to make it more clear how important the message really is. (#797)
  • The RTR client metrics have been extended by three new values allowing to track the time since last cache reset and the number of reset and serial queries. Like all RTR client metrics, these new values are only available if enable explicitly via the rtr-client-metrics config option. (#800)
  • TCP keepalive is now enabled for RRDP connections. The keepalive duration can be configured via the new command line and config file option rrdp-tcp-keepalive. (#801)

Bug Fixes

  • Fixed an issue in error handling in the RRDP collector that causes Routinator to exit if it encountered malformed Base 64 in RRDP snapshot and delta files. (Found by Donika Mirdita and Haya Shulman. Assigned [CVE-2022-3029].) ([#784])
  • Fixed an issue where RRDP snapshots and deltas with a status code other than 200 OK were accepted and processed. (#802)
  • Changed how Routinator deals with files in the store that cannot be parsed. These will now be ignored and the publication point stored in them considered not available. (#803)
  • When piping output from the vrps command into something else, a broken pipe will not lead to an error message any more. (#807)
  • Fixed various issues with the calculation of RTR metrics. (#811)

Other Changes

  • The minimal required Rust version has been increased to 1.60. (#792)
  • The default Docker image now listens on both port 8323 and 9556 for HTTP requests. (#809)

0.12.0-rc1

02 Nov 13:56
080b25c
Compare
Choose a tag to compare
0.12.0-rc1 Pre-release
Pre-release

Breaking Changes

  • Restructured the TAL configuration in response to the dropped requirement to opt into the ARIN TAL.

    Routinator will now use the bundled RIR TALs directly unless told otherwise by the new --no-rir-tals command line and config option. The additional bundled TALs can be added via the new --tal command line and config option. Additionally, the TAL directory can still be used via the --extra-tals-dir option. The tal-dir option has been removed but will still be accepted – and ignored – in the config file only.

    The init command has been removed. (#796)

  • Changed the default configuration option for unsafe-vrps to accept and removed all logging or mentioning of unsafe VRPs in this case. (#761)

  • Setting the rsync-timeout option to 0 now disables the rsync timeout. (#798)

  • Refactored error handling. Routinator now logs the reason why an object failed verification or was otherwise rejected. (#755)

  • Removed the deprecated rrdp-disable-gzip configuration option. (#769)

New

  • The new limit-v4-len and limit-v6-len command line and config file options allow limiting the length of IPv4 and IPv6 prefixes, respectively, to be included in the VRP data set. (#810)
  • The new rrdp-fallback command line and config file option allows specifying the circumstances under which a failed RRDP fetch should result in using rsync instead. Supported polices are never for never falling back to using rsync, stale for the current behavior of falling back when RRDP has failed for some time, and new to only fall back for repositories where RRDP has never worked before. (#799)
  • In the extended jsonext output format, the information for VRPs and router keys derived from RPKI data has gained a new member "tal" that shows the name of the TAL this object was published under. (#765)
  • The log output to files, stderr, and the /log HTTP endpoint now includes the log level of the message to make it more clear how important the message really is. (#797)
  • The RTR client metrics have been extended by three new values allowing to track the time since last cache reset and the number of reset and serial queries. Like all RTR client metrics, these new values are only available if enable explicitly via the rtr-client-metrics config option. (#800)
  • TCP keepalive is now enabled for RRDP connections. The keepalive duration can be configured via the new command line and config file option rrdp-tcp-keepalive. (#801)

Bug Fixes

  • Fixed an issue in error handling in the RRDP collector that causes Routinator to exit if it encountered malformed Base 64 in RRDP snapshot and delta files. (Found by Donika Mirdita and Haya Shulman. Assigned [CVE-2022-3029].) ([#784])
  • Fixed an issue where RRDP snapshots and deltas with a status code other than 200 OK were accepted and processed. (#802)
  • Changed how Routinator deals with files in the store that cannot be parsed. These will now be ignored and the publication point stored in them considered not available. (#803)
  • When piping output from the vrps command into something else, a broken pipe will not lead to an error message any more. (#807)
  • Fixed various issues with the calculation of RTR metrics. (#811)

Other Changes

  • The minimal required Rust version has been increased to 1.60. (#792)
  • The default Docker image now listens on both port 8323 and 9556 for HTTP requests. (#809)

0.11.3

13 Sep 12:02
8a94ce8
Compare
Choose a tag to compare

This is an important security release. All users of Routinator 0.9.0 up to 0.11.2 are encouraged to upgrade at their earliest convenience.

Bug Fixes

  • Fixes an issue in error handling in the RRDP collector that causes
    Routinator to exit if it encountered malformed Base 64 in RRDP snapshot
    and delta files. (Found by Donika Mirdita and Haya Shulman. Assigned
    CVE-2022-3029.) (#781)

0.11.2

20 Apr 11:31
a5e347d
Compare
Choose a tag to compare

Bug Fixes

  • Fixes an issue that caused the RTR server to possibly skip over some withdrawn VRPs in response to a serial query. (Found by Jay Borkenhagen, #747)

0.11.1

07 Apr 11:08
236f444
Compare
Choose a tag to compare

New

  • The dump command now also copies the stored trust anchor certificates. The certificates are named in the same way as they are internally using the hash over their URI. Please consult the manual for details. (#740)

Bug Fixes

  • The dump command now removes the internal header before copying the objects retained by the RRDP collector, i.e., the files copied into the rrdp sub-directory now contain the actual DER encoded data only. (#735)
  • Correctly set the idle time for TCP keepalives on incoming RTR connections on systems that support it. (#736)
  • Fix an encoding error in the /delta-json output. (#737)
  • Truncate the PID file before writing the current PID to it. (#738)
  • Exit with a status of 1 if an error happened. (#739)

0.11.1-rc1

04 Apr 12:44
f0afc8a
Compare
Choose a tag to compare
0.11.1-rc1 Pre-release
Pre-release

New

  • The dump command now also copies the stored trust anchor certificates. The certificates are named in the same way as they are internally using the hash over their URI. Please consult the manual for details. (#740)

Bug Fixes

  • The dump command now removes the internal header before copying the objects retained by the RRDP collector, i.e., the files copied into the rrdp sub-directory now contain the actual DER encoded data only. (#735)
  • Correctly set the idle time for TCP keepalives on incoming RTR connections on systems that support it. (#736)
  • Fix an encoding error in the /delta-json output. (#737)
  • Truncate the PID file before writing the current PID to it. (#738)
  • Exit with a status of 1 if an error happened. (#739)