From martin at nlnetlabs.nl Wed Jan 2 10:28:02 2019 From: martin at nlnetlabs.nl (Martin Hoffmann) Date: Wed, 2 Jan 2019 11:28:02 +0100 Subject: [RPKI] Suggestion for Watchdog method to always ensure routinator is running In-Reply-To: <8dc95238-cd5b-2f3c-a721-d0cc8c7afa18@netravnen.de> References: <8dc95238-cd5b-2f3c-a721-d0cc8c7afa18@netravnen.de> Message-ID: <20190102112802.36665a0b@glaurung.nlnetlabs.nl> Christoffer Hansen wrote: > > Do any subscriber to this list have any good idea's for ensuring > Routinator is always started after a reboot or when the daemon for > $_reasons crashed? This depends a bit on the operating system/distribution you are using. For most Linux-y things, systemd should take care of all of that. Creating a unit file for Routinator should be relatively straightforward. We mostly haven?t done that because the various distributions differ slightly where they keep stuff, so this should really be part of the packaging for a specific distribution. For FreeBSD, I am not sure if their init system automatically restarts disappearing daemons. We'll have a look into the possibility of enabling Routinator as a daemon as part of the existing port. > @NLnetLabs: Would be nice if you could document|recommend|suggest a > method together with the current instructions to get routinator up and > running for the above described case. ;) Ideally, Routinator would become part of the usual packaging for various systems and distributions. We would prefer someone to do that who is familiar with these systems, though, to ensure they meet necessary standards. Happy new year, everyone, and kind regards, Martin From martin at nlnetlabs.nl Fri Jan 4 11:15:38 2019 From: martin at nlnetlabs.nl (Martin Hoffmann) Date: Fri, 4 Jan 2019 12:15:38 +0100 Subject: [RPKI] =?utf-8?b?Um91dGluYXRvciAwLjIuMSDigJhSYXRlZCBS4oCZIHJl?= =?utf-8?q?leased?= Message-ID: <20190104121538.06ff087d@glaurung.nlnetlabs.nl> Dear mailing list, happy new year! Having recovered from the festivities, we can announce our first Routinator release of 2019, version 0.2.1 ?Rated R.? Routinator is an RPKI relying party software that collects and validates statements made in the Resource Public Key Infrastructure (RPKI) about allowed route origins and provides them to routers and concerned Internet citizens. This release primarily fixes two bugs introduced with the configuration file support in 0.2.0. For one, Routinator failed to build on 32-bit systems. Secondly, the code and documentation disagreed on the name of the default configuration file. After checking back with users, settled on `$HOME/.routinator.conf`. However, since that didn?t seem enough to warrant a release in itself, we decided to try and make Routinator work on Windows as a bonus. Because of Rust?s built-in support for Windows, this turned out easier than expected. You still need to get `rsync`, though, in particular the one coming with Cygwin. You can read about all the changes in this release in the complete Changelog [0]. Happy Routinating, Martin [0] https://github.com/NLnetLabs/routinator/blob/master/Changelog.md From alex at nlnetlabs.nl Mon Jan 7 09:13:16 2019 From: alex at nlnetlabs.nl (Alex Band) Date: Mon, 7 Jan 2019 10:13:16 +0100 Subject: [RPKI] Mozilla Open Source Support programme awards grant for the Routinator Message-ID: <570A2740-84AA-4C4B-93BA-B5A46D6A90E7@nlnetlabs.nl> Dear mailing list, We are incredibly excited to announce that the Mozilla Open Source Support (MOSS) programme [1] has awarded a grant for the development of the Routinator, NLnet Labs? RPKI Relying Party software that helps make Internet routing more secure. The MOSS awards programme supports open source projects that contribute to Mozilla?s work and the health of the Internet. Specifically for the MOSS Mission Partners track, Mozilla looks for projects that are closely aligned with its own mission. We are also very grateful to the Amsterdam Internet Exchange (AMS-IX), who endorsed us during the application process. AMS-IX was one of the world?s first Internet Exchanges to offer RPKI-based filtering on their route server platform. With the MOSS award, we will be able to develop the Routinator into a lean, stable and feature-rich RPKI relying party package. Over the course of 2019, we will be providing packages for major Operating Systems, integration with alerting and monitoring services, configuration management, a web-based user interface, a RESTful API and much more. We also want to take this opportunity to thank Mozilla for their pivotal role in supporting the Rust programming language. The RPKI toolset, which includes the Routinator, is the first major project that we are building exclusively in Rust. At its core Rust is a systems language that combines C level performance with modern high level elements, such as a strong type system, error handling, and concurrency. Besides all this the Rust build system and dependency management system are superb. Mozilla is the fourth organisation to join in funding the development of our RPKI toolset. This kind of community support is incredibly valuable to a non-profit foundation like ours. It enables us to commit long term resources to the project and build it to the standards that you have come to expect from NLnet Labs. Hoping that 2019 will be an amazing year for RPKI and routing security. Cheers, Alex [1] https://www.mozilla.org/en-US/moss/