[Bug 258041] net/routinator: Update to 0.10.0

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 25 Aug 2021 13:31:18 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258041

            Bug ID: 258041
           Summary: net/routinator: Update to 0.10.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://www.nlnetlabs.nl/news/2021/Aug/23/routinator-0
                    .10.0-released
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: jaap@NLnetLabs.nl
 Attachment #227425 maintainer-approval+
             Flags:

Created attachment 227425
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227425&action=edit
patch to upgrade

0.10.0  'Through Many Dangers, Toils, and Snares'

Breaking changes

* Data is now stored directly in the file system again. This returns
  memory consumption to pre-0.9 levels. All improvements to
  robustnesshave been maintained. (#590, #601, #604)

* The json and jsonext output formats now include a metadata object
  that contains the time the data set was created in the generated
  and generatedTime fields as Unix and ISO time stamps, respectively.
  (#605)

* The JSON output of the validate command and the of the /validity
  HTTP endpoint now include a generatedTime field that provides the
  generation time of the data set that was used for validation as
  an ISO time stamp. (#605)

* The default RRDP timeout (via the rrdp-timeout option) has been
  increased to 300 seconds. (#612)

New

* The maximum over delta steps performed during an update of an
  RRDP repository is now be limited via the rrdp-max-delta option.
  If more steps are necessary, the snapshot is used instead. This
  will improve the update times in cases where Routinator isn
  running constantly. The default limit is 100 steps. (#615)

* It is now possible to disable the use of the gzip transfer encoding
  in the RRDP client via the new rrdp-disable-gzip option. (#602)

* The start of a validation run is now logged as an info message. (#609)

* A reference to the global help appears now at the end of a
  sub-command  help message. (#607)

* A summary of the data set similar to the summary output format
  is now logged at log level info at the end of a validation run.
  (#617)

* Strict checking for address and prefix lengths in certificates,
  and for prefix and max-length in ROAs. (via rpki #154, based on
  an error report by @job)

Bug Fixes

* Catch and log error output from rsync. (#577)

* Local exception files that contain prefix assertions with a shorter
  max-length than the prefix length are now rejected instead of
  addingthese invalid prefix assertions to the output data set. (#608)

* The rrdp-timeout command line option was setting both the RRDP
  timeout and the RRDP connection timeout. Now the rrdp-connect-timeout
  is correctly used for the latter. (Note: The config file was using
  the correct keys.) (#611)

* Added --rrdp-fallback-time option to the command line parser. It
  was documented and supposed to be present previously, but wasn't. (#614)

* The RTR server now returns the correct PDU as a cache reset
  response, which is returned when the server cannot provide a delta
  update to a client. Previously, a broken End of Data PDU was
  returned.  (Via rpki #151.)

* Make parsing of local exception files much more strict to avoid
  introducing illegal VRPs into the data set. Parsing will now fail
  if any aspect of a prefix or prefix assertion is incorrect. This
  includes a non-zero host portion of a prefix. (#627)

Other

* In the JSON metrics for RRDP repositories, the fields serial,
  session, delta, and snapshotReason are left out entirely when the
  server reported not changes via a 304 response. (#613)

-- 
You are receiving this mail because:
You are the assignee for the bug.