Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 May 2020 19:47:35 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 246267] [MAINTAINER] net/routinator: Update to version 0.7.0
Message-ID:  <bug-246267-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246267

            Bug ID: 246267
           Summary: [MAINTAINER] net/routinator: Update to version 0.7.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: jaap@NLnetLabs.nl
 Attachment #214211 maintainer-approval+
             Flags:

Created attachment 214211
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D214211&action=
=3Dedit
patch to update

0.7.0 =E2=80=98Your Time Starts =E2=80=A6 Now=E2=80=99

Breaking Changes

o Routinator now filters out rsync URIs and RRDP URIs that contain
  dubious host names that should not be present in the public RPKI.
  In this version they are =E2=80=98localhost,=E2=80=99 any IP address, and=
 any URI
  with the port explicitly specified. This filter can be disabled
  via the --allow-dubious-hosts command line and config option for
  test deployments. (#293)

0 Only CRLs mentioned on the manifest are now considered when
  checking any published objects except for the manifest itself.
  If the hash of the CRL on the manifest does not match the CRL,
  it is rejected. Objects referencing a CRL that is not on a manifest
  or has a hash mismatch are rejected. [(#299)]

o The minimal supported Rust version is now 1.39.0.

New

0 The new option --stale allows selecting a policy for dealing with
  stale objects =E2=80=93 i.e., manifests and CRLs that are past their
  next-update date. The policies are reject, warn, and accept. The
  previous hard-coded policy of warn, i.e., accept but log a warning,
  is the default. (#288)

0 New output formats bird and bird2 which produce a roa table for
  Bird 1 and a route table for Bird 2, respectively. (#290, by
  @netravnen)

0 New output format csvcompat which produces CSV output as similar
  to that of the RIPE NCC Validator as possible. (#292)

0 The new config file option tal-labels allows defining explicit
  names to be used when TALs are referenced in output. This way,
  the output can be made to be even more similar to that produced
  by the RIPE NCC Validator. (#291)

0 The csvext output format is now also available via the HTTP server
  at the /csvext path. (#294)

0 New metrics for the status of the RTR and HTTP servers. (#298)

0 New metric of the number of stale objects encountered in the last
  validation run. (#298)


Other Changes

0 Update to Rust=E2=80=99s new asynchronous IO framework for the RTR and
  HTTP servers. Repository synchronization and validation remain
  synchronous atop a thread pool. (#282)

0 Changed concurrency strategy for repository update and validation.
  Previously, each trust anchor was updated and validated synchronously.
  Now processing of a CA is deferred if its repository publication
  point hasn=E2=80=99t been updated yet. Processing is then picked up by
  the next available worker thread. This should guarantee that all
  worker threads are busy all the time. ([#284)]

0 Optimized what information to keep for each ROA, bringing maximum
  memory consumption down to about a quarter. (#293)

o The Docker image now wraps Routinator into tini for properly
  dealing with signals and child processes. (#277)

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246267-7788>