rust/rfb: use consistent key name for security_result

A typo caused a slightly different key (`security-result`) to be used
for the case in which the result was `FAIL`. This commit addresses this
by ensuring the same string is used for all cases.

Ticket: #7198

diff --git a/rust/src/rfb/logger.rs b/rust/src/rfb/logger.rs
index 62bb20966fe788eb762c9904a54daa9e9018e789..8c8e2ca2ed555f5d764bd63f653f46f49fbc5145 100644 (file)
--- a/rust/src/rfb/logger.rs
+++ b/rust/src/rfb/logger.rs
@@ -67,12 +67,13 @@ fn log_rfb(tx: &RFBTransaction, js: &mut JsonBuilder) -> Result<(), JsonError> {
         _ => (),
     }
     if let Some(security_result) = &tx.tc_security_result {
+        let result_key = "security_result";
         let _ = match security_result.status {
-            0 => js.set_string("security_result", "OK")?,
-            1 => js.set_string("security-result", "FAIL")?,
-            2 => js.set_string("security_result", "TOOMANY")?,
+            0 => js.set_string(result_key, "OK")?,
+            1 => js.set_string(result_key, "FAIL")?,
+            2 => js.set_string(result_key, "TOOMANY")?,
             _ => js.set_string(
-                "security_result",
+                result_key,
                 &format!("UNKNOWN ({})", security_result.status),
             )?,
         };