Bug 236324 - [MAINTAINER] net/routinator Update to 0.3.1
Summary: [MAINTAINER] net/routinator Update to 0.3.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Steve Wills
Depends on:
Reported: 2019-03-06 16:02 UTC by Jaap Akkerhuis
Modified: 2019-03-07 15:47 UTC (History)
0 users

See Also:

patch to update (22.05 KB, patch)
2019-03-06 16:02 UTC, Jaap Akkerhuis
jaap: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jaap Akkerhuis 2019-03-06 16:02:26 UTC
Created attachment 202655 [details]
patch to update

0.3.1 ‘More Intensity’


TAL files will only be read once when Routinator starts. This improves robustness at the cost of having to restart Routinator when the TALs change. (#74)

New option --rsync-timeout setting the maximum number of seconds any rsync command is allowed to run. This prevents hanging rsync from blocking Routinator. (#76)

Additional Prometheus metric valid_roas reporting the number of verified ROAs. 
Additionally, both metrics are now reported separately for each TAL. (#78)

Compare RTR serial numbers according to RFC 1932. (#81)

Bug Fixes

A missing tcp-listen option in the config file caused Routinator to crash in rtrd mode instead of using the default socket. (#80)

Decoding manifest and ROAs now checks that the content type field in the signed object has the correct object identifier. (rpki-rs #27)
Comment 1 commit-hook freebsd_committer 2019-03-07 15:46:20 UTC
A commit references this bug:

Author: swills
Date: Thu Mar  7 15:45:55 UTC 2019
New revision: 494958
URL: https://svnweb.freebsd.org/changeset/ports/494958

  net/routinator: update to 0.3.1

  PR:		236324
  Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)

Comment 2 Steve Wills freebsd_committer 2019-03-07 15:47:00 UTC
Committed, thanks!