From 25893d233ce7d1000e4c31dda5681baaab68b18f Mon Sep 17 00:00:00 2001 From: riccardom Date: Fri, 9 Oct 2026 09:50:32 +0200 Subject: [PATCH] [client] status: spell out Rosenpass in the quantum-resistance mechanism line The mechanism summary used "RP strict" / "RP permissive" while every other surface (JSON keys, config, per-peer text) spells out "Rosenpass". Use "Rosenpass strict" / "Rosenpass permissive" for consistency. Found in cubic review on #7098 (client/status/status.go:779). --- client/status/status.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/client/status/status.go b/client/status/status.go index 96527fa04..7ec5d2d7a 100644 --- a/client/status/status.go +++ b/client/status/status.go @@ -766,7 +766,7 @@ func ToProtoFullStatus(fullStatus peer.FullStatus) *proto.FullStatus { } // quantumResistanceMechanism reports which post-quantum mechanism the local client runs, -// as an enum: "none", "ML-KEM strict", "ML-KEM permissive", "RP strict", "RP permissive". +// as an enum: "none", "ML-KEM strict", "ML-KEM permissive", "Rosenpass strict", "Rosenpass permissive". // ML-KEM and Rosenpass are mutually exclusive, so at most one is active; ML-KEM takes // precedence if somehow both are set. Strict/permissive is the fail-closed vs fail-open mode. func quantumResistanceMechanism(rosenpassEnabled, rosenpassPermissive, mlkemEnabled, mlkemStrict bool) string { @@ -776,9 +776,9 @@ func quantumResistanceMechanism(rosenpassEnabled, rosenpassPermissive, mlkemEnab case mlkemEnabled: return "ML-KEM permissive" case rosenpassEnabled && !rosenpassPermissive: - return "RP strict" + return "Rosenpass strict" case rosenpassEnabled: - return "RP permissive" + return "Rosenpass permissive" default: return "none" }