sendnrw/netbird
2
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-10-09 23:19:11 +02:00
Code Issues Packages Projects Releases Wiki Activity

[client] status: spell out Rosenpass in the quantum-resistance mechanism line

Browse Source 
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).
This commit is contained in:
riccardom
2026-10-09 09:50:32 +02:00
parent 85eaf4319d
commit 25893d233c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
client/status/status.go
+3 -3
View File
@@ -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"
}