Date: Fri, 13 Sep 2019 12:44:56 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 240560] [MAINTAINER] net/routinator: Update to version 0.6.1 Message-ID: <bug-240560-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240560 Bug ID: 240560 Summary: [MAINTAINER] net/routinator: Update to version 0.6.1 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: jaap@NLnetLabs.nl Attachment #207460 maintainer-approval+ Flags: Created attachment 207460 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D207460&action= =3Dedit Patch to update Changes in the Port: This update is actually combined with a bug fix. I also aidded the feature request as discussed in PR #239899 Release notes: 0.6.1 `Philosophy Is Tricky' This is a bug fix release that primarily fixes an issue in 0.6.0 whereby the serial number for RTR was not updated when new data became available resulting in RTR clients getting stuck with old data. __________________________________________________________________ New * RRDP access statistics are now also shown in the /status HTTP endpoint. They were already part of the Prometheus metrics. (#218) Bug Fixes * The RTR serial number was not increased when new data became available. (#215) Other changes * The RRDP client will not complain if it can read a non-existing state file anymore as this is a completely normal situation. (#217) 0.6.0 `Pink Sombrero' This release adds support for the RPKI Repository Delta Protocol (RRDP), an alternative method of fetching RPKI data that uses HTTPS instead of rsync. RRDP will speed up synchronisation for frequently updated repositories, for instance when Routinator is running in server mode. For the RRDP implementation, most of the internal logic of Routinator has been rewired. We used this opportunity for extensive refactoring and cleanup of the code base. One user visible consequence is that the listeners for RTR and HTTP are now started immediately instead of waiting until after the first validation run. They still will report an error message until then, but at least you won have to wonder whether something went wrong anymore. __________________________________________________________________ Breaking Changes * Removed the rsync-count command line and configuration file option. This option is now unused as modules are now rsynced only when they are actually accessed. (#187) * The default value for refresh has been lowered to 600 seconds. (#191) * The refresh time placed in the RTR End-of-data PDU is now calculated from the time until the next validation run is expected to finish. (#193) * The listeners for RTR and HTTP in server mode are now started right away and report an error until the first validation has finished. (#203) New * Routinator now supports RRDP for synchronizing repository content. (#187) * Restructured repository directory. The rsync data now lives in a sub-directory called rsync. The main repository directory will now be kept clean and all unexpected files removed. (#187) * In server mode, the repository will be refreshed and re-validated when the first object expires. (#191) * Protection against loops in the CA structure: Routinator checks that any subject key identifier only appears once in the chain from a trust anchor to a CA certificate. (#192) * Routinator now explicitly skips .cer files that aren CA certificates before even trying to validate them. This already happened before because these files failed validation. (#194) * New options user and group for setting the user and group names a detached server process should be run as. (#213) Bug Fixes * Fixed crash if the TAL directory is empty. Routinator will complain but run since there could be local exceptions. (#212) --=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-240560-7788>