Release 0.3.2-rc1. (#139)

New

* Add ASPA support to JSON input and output. ([#132] by [@devsnek])
* ASPA JSON compatibility with krill & routinator ([#134] by [@ember-ana])
* The `json` can now use the native TLS implementations of Windows and
  macOS. This needs to be enabled during compile time through the
  `native-tls` feature and then for a unit through the new `native-tls`
  option. When enabled, this uses TLS via OpenSSL rather than Rustls on
  other systems. ([#137])
* The `json` unit can now be forced to stick to TLS 1.2 or less via the
  new `tls-12` option. ([#137])

Bug fixes

* Fix rtr-tls target having certificate and key options reversed. ([#133]
  by [@ember-ana])
* Fixes to RTR handling via [rpki-rs 0.18.6].
* The `working-dir` option was accidentally used as the path for the PID
  file. Now the `pid-file` option is used as intended. (via
  [daemonbase 0.1.3])

Other changes

* The minimum supported Rust version is now 1.81. ([#138])

Author: partim

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "rtrtr"
-version = "0.3.2-dev"
+version = "0.3.2-rc1"
 edition = "2021"
 rust-version = "1.81.0"
 authors = ["NLnet Labs <rpki-team@nlnetlabs.nl>"]
@@ -15,9 +15,9 @@ arbitrary       = { version = "1", optional = true, features = ["derive"] }
 arc-swap        = "1"
 bytes           = "1"
 chrono          = "0.4.31"
-clap            = { version = "4.4", features = [ "cargo", "derive" ] }
+clap            = { version = "4", features = [ "cargo", "derive" ] }
 crossbeam-utils = "0.8.4"
-daemonbase      = "0.1.2"
+daemonbase      = "0.1.3"
 futures-util    = "0.3"
 http-body-util  = "0.1"
 hyper           = { version = "1.3.1", features = [ "server" ] }

Cargo.toml

@@ -1,8 +1,8 @@
 # Change Log
 
-## Unreleased next version
+## 0.3.2-rc1
 
-Breaking changes
+Released 2025-04-24.
 
 New
 
@@ -21,6 +21,9 @@ Bug fixes
 * Fix rtr-tls target having certificate and key options reversed. ([#133]
   by [@ember-ana])
 * Fixes to RTR handling via [rpki-rs 0.18.6].
+* The `working-dir` option was accidentally used as the path for the PID
+  file. Now the `pid-file` option is used as intended. (via
+  [daemonbase 0.1.3])
 
 Other changes
 
@@ -34,6 +37,8 @@ Other changes
 [@devsnek]: https://github.com/devsnek
 [@ember-ana]: https://github.com/ember-ana
 [rpki-rs 0.18.6]: https://github.com/NLnetLabs/rpki-rs/releases/tag/v0.18.6
+[daemonbase 0.1.3]: https://github.com/NLnetLabs/daemonbase/releases/tag/v0.1.3
+
 
 
 ## 0.3.1 ‘Some Checks Haven’t Completed Yet’

Changelog.md

@@ -44,7 +44,7 @@ ARG MODE=build
 # ========
 #
 # Only used when MODE=build.
-ARG BASE_IMG=alpine:3.18
+ARG BASE_IMG=alpine:3.21
 
 
 # CARGO_ARGS

Dockerfile

@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "RTRTR" "1" "Jan 09, 2025" "0.3.2-dev" "RTRTR"
+.TH "RTRTR" "1" "Apr 24, 2025" "0.3.2-rc1" "RTRTR"
 .SH NAME
 rtrtr \- RPKI data proxy
 .SH SYNOPSIS
@@ -258,6 +258,20 @@ authentication.
 .sp
 The certificate is used when communicating with an HTTPS server to
 fetch the JSON data.
+.TP
+.B tls\-12
+A boolean value specifying whether the maximum TLS version to use when
+fetching an \fBhttps:\fP URI should be TLS 1.2. If this value is missing
+or \fBfalse\fP, TLS 1.3 is used as well.
+.TP
+.B native\-tls
+A boolean value specifying whether the native TLS implementation should
+be used when fetching \fBhttps:\fP URIs. If enabled, RTRTR will use
+SChannel on Windows, Security.framework on macOS, and OpenSSL
+anywhere else. Otherwise, Rustls is used everywhere.
+.sp
+This option is only available if RTRTR was explicitly build with the
+\fBnative\-tls\fP feature flag.
 .UNINDENT
 .SH ANY UNIT
 .sp