WEBDIENSTE/NLnetLabs-krill
1
0
Fork 0
mirror of https://github.com/NLnetLabs/krill.git synced 2026-09-23 18:04:54 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update release version for 0.9.0-rc2

Browse Source
This commit is contained in:
Tim Bruijnzeels
2021-05-12 11:26:23 +02:00
parent 1a2875bfda
commit 348bb47217
3 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Cargo.lock
Generated
+1 -1
View File
@@ -1112,7 +1112,7 @@ dependencies = [
[[package]]
name = "krill"
version = "0.9.0-dev"
version = "0.9.0-rc2"
dependencies = [
"base64 0.13.0",
"basic-cookies",
Cargo.toml
+1 -1
View File
@@ -1,7 +1,7 @@
[package]
# Note: some of these values are also used when building Debian packages below.
name = "krill"
version = "0.9.0-dev"
version = "0.9.0-rc2"
edition = "2018"
authors = [ "The NLnet Labs RPKI team <rpki-team@nlnetlabs.nl>" ]
description = "Resource Public Key Infrastructure (RPKI) daemon"
Changelog.md
+10 -2
View File
@@ -1,6 +1,6 @@
# Change Log
## 0.9.0 RC
## 0.9.0 RC 2
Welcome to the Krill 0.9.0 Release Candidate.
@@ -21,7 +21,7 @@ migration of course, but still we would very much like to encourage existing use
this further on real data.
In order to test the upgrade you can do the following:
- install Krill 0.9.0-rc1 on a test machine
- install Krill 0.9.0-rc2 on a test machine
- copy over your existing data directory, but exclude the `keys` directory
- set the ENV variable KRILL_UPGRADE_ONLY
- start krill v0.9.0-rc1 using your copied data directory
@@ -162,6 +162,14 @@ the rather unlikely case that a parent CA temporarily removed one of your resour
Let the Publication Server write the notification.xml file to a new file, and then rename it.
This prevents that Relying Parties can retrieve a half-written file. (#352)
Logging is now much less noisy. And Krill CAs will report *which* new resources were received
from, or removed by a parent. As part of this change we also fix a harmless, but annoying, bug
in certificate request logic. Krill would wrongfully report that a parent had reduced the
eligible 'not after' time, when in fact it had extended it. Furthermore Krill will now request
a new certificate only if the new 'not after' time is more than 10% further into the future
compared to the current certificate - this is safe and will reduce noise levels where parent
CAs use a simple strategy which returns a new 'not after' time for every request. (#513, #514)
## 0.8.2 'Can't touch this'
As it turned out the previous release (0.8.1) still insisted on cleaning up 'redundant ROAs'